Adopting Jakarta EE
Now that Jakarta EE's official launch is upon us, you could expect that developers, whether or not they are on a Java EE project, are looking forward to this moment. At least, I certainly am! However, I have spoken to a few acquaintances and colleagues that are currently on a Java EE 7 or Java EE 8 project. What surprised me is that not all of them are actually busing themselves with plans for adopting Jakarta EE. How is that possible and why aren't they? Let's see what their responses were, placed in three categories.
Jakarta EE...is that really a thing?
It may sound unlikely, but some don't even seem to have the knowledge that there is a new platform as a successor for Java EE on the rise. Meanwhile, they may be busing themselves with fixing issues, optimizing their business logic and perform maintenance, instead of planning to adopt the next level of their platform. Of course, this can be a valid situation, but what could they gain if they started adopting Jakarta EE?
Java EE 7/8 works pretty well for us. Why hurry?
Apparently, Java EE 7 or 8 is already such a feature-rich platform for some developers that they are just not in a hurry to adopt Jakarta EE. Although it is a perfectly valid choice when people are content with their current situation, maybe diving into the upcoming features of Jakarta EE will spark their interest in adopting them?
...I was just planning to adopt a competitor
The fact that the focus on the Java EE platform was low for a couple of years has some developers believe that competitors are ahead of the Jakarta EE platform. Although this situation cannot be denied as we look at the current state of the platform, it also cannot be confirmed and is likely just a misinterpretation.
As we speak, talks are being given at conferences by various developers and spokespeople of the Jakarta EE platform or brand that prove how modern, feature-rich and even cloud-native the platform is. Please consider using their knowledge of the evolution of the platform to your advantage before you make the choice of moving to a competitor.
What is your plan for adopting Jakarta EE?
If you are reading this, I'm curious if you are in one of these situations, or are just completely new to the platform. Therefore, I would like to know how you feel about adopting the Jakarta EE platform. Do you have any doubts or pitfalls in the process? Or maybe you are fully into it and want to share the progress you are making? Whatever your situation is, please share your case with us!
About the Author
