Understanding Jakarta EE: “Jakarta EE tools should support Kubernetes”
Confused about what’s going on with Jakarta EE? This interview series is meant to help you navigate through all the changes and understand where it’s headed, as well as how Jakarta EE plans to become the new home of cloud-native Java. Our tenth guest is Otávio Santana, Senior Software Engineer at Tomitribe. Let’s dive deeper into the Jakarta EE universe!
Jakarta EE: The story so far
Transfering Java EE technologies from Oracle to the Eclipse Foundation is no easy job. The Jakarta EE brand is evolving rapidly but we need to stop for a minute and acknowledge all the changes and plans which will include the platform’s evolution into cloud, containers, microservices, serverless, and reactive technologies.
The vision for the technical future of Jakarta EE includes the following:
- Enhanced support for microservices architecture
- Move to Cloud Native Java, which includes better integrations with technologies like Docker and Kubernetes
- Increase the pace of innovation
- Build a vibrant developer community
- Provide production quality reference implementations
Update: The results of the Participant and Committer Member elections for representatives to the Jakarta EE Working Group Steering Committee, Specification Committee, and Marketing & Brand Committee have just been announced.
- Specification Committee – Participant: Alex Theedom (LJC)
- Specification Committee – Committer Member: Werner Keil
- Marketing & Brand Committee – Participant: Simon Maple (LJC)
- Marketing & Brand Committee – Committer Member: Ivar Grimstad
- Steering Committee – Participant: Martijn Verburg (LJC)
- Steering Committee – Committer Member: Ivar Grimstad
If you want to learn more about the Jakarta EE Working Group governance and processes, have a look at the Jakarta EE Working Group Charter page.
Now back to our series! Keeping track of what’s in and what’s out is still a work in progress, but here’s what we know for certain. While there may be some other proposals that are still pending, these are the projects that have been accepted. This list should help you keep track of Jakarta EE’s progress but we’ve only scratched the surface.
What are the current and future challenges of Jakarta EE? How is it forging a new path forwards for enterprise Java? Where is it headed? This interview series is meant to help you navigate through all the changes and understand where it’s headed, as well as how Jakarta EE plans to become the new home of cloud-native Java.
Jakarta EE series: Here are the interviews published so far
- David Heffelfinger: “I wouldn’t like to see Jakarta EE tied to any specific container orchestration tool”
- Markus Eisele: “I strongly believe there is a lot to do to make Jakarta EE ready for the future”
- Josh Juneau: “The platform needs to evolve more dynamically than it had done in the past”
- Werner Keil: “Jakarta EE should become more modular than it is right now”
- Ondrej Mihalyi: “MicroProfile is paving the way for better microservices support in the Jakarta EE ecosystem”
- Reza Rahman: “Modularity is key to faster release cycles”
- Dmitry Kornilov: “Jakarta EE APIs should be more cloud-friendly”
- Arjan Tijms: “Recognizing the importance of Kubernetes likely means a further reduction in the importance of running multiple applications on a single Jakarta EE server”
- Richard Monson-Haefel: “Jakarta EE 9 will begin the transition to a simpler, lighter, and more flexible platform”
Now it’s time to welcome our next guest, Otávio Gonçalves de Santana, Senior Software Engineer at Tomitribe. Let’s dive deeper into the Jakarta EE universe!
JAXenter: Would it be a good idea to merge Eclipse MicroProfile with Jakarta EE?
Otávio Santana: Although MicroProfile and Jakarta EE need to work together, they will not be merged into the same top level project; Eclipse MicroProfile and Jakarta EE have different objectives. The former has the philosophy of innovation and rapid iteration, so failing faster is essential to a healthy innovation process.
The next steps in Eclipse MicroProfile are: reach a consensus among vendors and community and then standardize. Once at the last stage, the best fit for it is in Jakarta EE. I look at Eclipse MicroProfile as an “innovation playground” and when the project is mature enough to become a standard, it moves forward to Jakarta EE.
JAXenter: Jakarta EE’s path has already been chosen, and that’s cloud-native. How will this goal be achieved?
Otávio Santana: The Jakarta EE community will achieve its goals in the same way it has always achieved goals, through unity and cooperation. It’s a fantastic community.
The microservices support will come from the adoption of the Eclipse MicroProfile standards.
JAXenter: How can Jakarta EE evolve to meet users’ cloud needs?
Otávio Santana: Jakarta EE will evolve by creating an open, transparent, and inclusive community that encourages collaboration in every aspect of the project. Transparency through open email lists, a welcoming atmosphere, and surveys will help ensure that the project is always aligned with the needs of its community.
JAXenter: Let’s focus on the Jakarta EE survey results. Over 60% of the respondents want better support for microservices. How would you implement that?
Otávio Santana: The microservices support will come from the adoption of the Eclipse MicroProfile standards. Eclipse MicroProfile is adding new projects and many of them, when ready, can be adopted by Jakarta EE to fulfill its microservices objectives.
JAXenter: Speaking of the survey, the second most desired aspect is native integration with Kubernetes. Should this be a priority for the development of the project?
Otávio Santana: Yes, Jakarta EE tools should support Kubernetes. The industry is moving into the cloud and Kubernetes is a big part of that.
JAXenter: Would you prefer faster releases (like Java’s new release cadence) or slower, yet bigger feature releases?
Otávio Santana: I believe in releases that are delivered regularly. However, faster versions such as every six months do not make sense. Using the newest survey from Eclipse Foundation, 86% of the community is still using Java 8, yet the Java 11 is due to be released soon. My suggestion would be hybrid cadency releases with a fix and small features every three months and a big release every two years following the JDK LTS, to conclude, the JDK support should follow the JDK LTS as well.
SEE ALSO: Java EE 8: the baseline of Jakarta EE
JAXenter: How do you plan to participate in the development process of Jakarta EE? Any specs or TCKs you’re especially interested in?
Otávio Santana: I plan to maintain projects that already exist, such as JSON-B and also CDI, and help move them forward. I believe there are improvements that can be made to existing projects as well as defining new ones.
I’m interested in high scalability applications, and integrations with NoSQL, map-reduce, reactive programming will be my target to help in Jakarta EE.
JAXenter: How do you think the community should adapt to the changes that have taken place recently?
Openness and transparency will ensure that Jakarta EE thrives as an open standard and project.
Otávio Santana: With enthusiasm! The platform will continue to evolve and become more open and transparent at the Eclipse Foundation. The process used to define the logo and trademark name is a great start. It was an open process that used surveys to determine the preferences of the community with regard to the name. Openness and transparency will ensure that Jakarta EE thrives as an open standard and project.
JAXenter: What’s next for Eclipse JNoSQL?
Otávio Santana: We, at Eclipse JNoSQL, are waiting, with anxiety, the definition of the process by which we can submit a specification to Jakarta EE. We’ve already seen rapidly growing support among NoSQL providers with more than a third of them adopting JNoSQL.
JAXenter: Could you please describe what this project is all about?
Otávio Santana: Eclipse JNoSQL is a Java framework that streamlines the integration of Java applications with NoSQL databases. It defines a set of APIs and provides a standard implementation for most NoSQL databases. This clearly helps to achieve very low coupling with the underlying NoSQL technologies used in applications. You can get more information about the project from the JAXenter article that I wrote.
Our Jakarta EE interview series is published three times a week. Join us on a journey to the depths of Jakarta EE!