jakartaee-nosql

How the community is making Java EE more relevant to the Cloud-native and Containers

Java turned 25 years old (24.05.2020) only a couple of days ago, 28 years old unofficially.

Java is more significant than whatever we think it is. Over the years, I developed applications for enterprise, web, and embedded devices. It suffices to say that you can develop anything that your creativity allows. If you find something that you can build in Java, please add it in the comments.

To celebrate the language anniversary, I invited Ivar Grimstad to join me on the #OffTheChain podcast. Ivar is a celebrity in the Java community as the Jakarta EE evangelist working at the Eclipse Foundation. The task of moving Java EE to the foundation made a great topic. Unless you have been living under a rock, Oracle has donated Java and its enterprise edition to various open-source bodies with some small caveats. As you can see in the interview, see the embedded video below, the legal side of things are causing delays and impairing the engineering innovation.

The Eclipse Foundation is hard at work in migrating the code to an open-source structure, legally speaking. The general availability of Jakarta EE is Jakarta EE 8, which is a straight port of the Java EE 8. If you are an enterprise client and you have Java EE 8 applications deployed, you can safely use Jakarta EE has it is 100% compatible. The next release is Jakarta EE 9, and developers beware as the release is not backwards compatible to Java EE 8 or Jakarta EE 8 as there is a change in the API namespace. It is one of those legal requirements, I am speculating here.

I am looking forward to Jakarta EE, and I cannot wait to see what features will be included. Fortunately, we do not have to wait that long as the community has also been hard at work. Some of the projects which are top of the list are:

–      Microprofile

–      Soteria

–      MVC 1.0

–      Micronaut and Quarkus

Microprofile is the one project which stands out the most with what they are trying to achieve, optimising enterprise Java for a Microservices Architecture. Microprofile has native support for telemetry and features required for cloud-native applications such as:

– Fault Tolerance

– JWT Auth

– Health Checks

– Open Tracing

– Metrics

– OpenApi

To name a few.

Micronaut and Quarkus are competing Java frameworks with their focus in reducing Java applications cold start time and memory footprints; two requirements for serverless architectures and environments such as AWS Lambda. I am a little biased towards Quarkus as I have a few projects using it.

Listening to Ivar and what he thinks is coming next to Jakarta EE. As the community innovates, the foundation standardises on the most popular features.

Add a Comment

Your email address will not be published. Required fields are marked *