coachingbad.blogg.se

Jakarta EE today is as simple as any platform can get.

However the pain inflicted by that iteration of the platform has lingered on. Mercifully those days have been gone for a long while now. This misconception has its root in the J2EE days. All I know is that a platform released more than two decades ago, that is still actively developed with this many APIs, isn't one that lacks any serious, major features.

Honestly I've no idea what "feature rich" means when used like this. Jakarta EE is microservices capable and ready. Pairing it with MicroProfile is the icing on the cake. For instance Jakarta EE 10comes with a core profile designed for smaller containerized runtimes. The platform itself, especially within the context of the latest version 10 release, is microservices ready. Jakarta EE is more than capable of being used in a microservicesarchitecture. This is another misconception that has plagued the platform for a while. Jakarta EE Cannot Be Used For Microservices Jakarta EE 10 for instance, came with a lot of new features and updates to almost every API on the platform. It simply adopts new technologies only after they have been tried and tested. This is what in some cases, gives rise to the notion that that the platform is outdated. And so a serious platform like Jakarta EE must carefully balance stability and backwards compatibility with new features. Enterprises require stability and predictability.

The root cause of this misconception partly lies in the frankly terrible comparison of a massive, far reaching platform like Jakarta EE to some "simple" Java frameworks.įor a platform used by companies of all sizes in all sectors in almost every country, Jakarta EE naturally will move at a different pace than a small framework. Needless to say, Jakarta EE is very much up to date. On social media sites like Reddit, I often see new Java developers asking about enterprise platforms, and there is almost always the obligatory "pick X but avoid Java EE because it is outdated." Unfortunately this mindset is very entrenched in the minds of a not so insignificant number of Java developers. This blog post aims to dispel some of these deeply rooted misconceptions about the Jakarta EE Platform, especially after the last major release. A natural consequence of this is that some notions about the platform arising from some of the past challenges that may have been true about past iterations have stuck. Over the years, it has had its fair share of challenges. The Jakarta EE Platform has come a long way since its debut as J2EE back the days of Sun Microsystems.