Jakarta EE takes the cloud-native Java path
© Shutterstock / VectorKnight
The results of the Jakarta EE community survey revealed that cloud-native development is a top requirement in the platform’s evolution, alongside the need for a faster pace of innovation on the Jakarta EE platform. Users’ wish has been granted! The Eclipse Foundation unveiled the new open source governance model and a “cloud-native Java” path for Jakarta EE.
The Eclipse Foundation conducted a survey of more than 1,800 Java developers worldwide last month to identify the community’s top priorities regarding the future of Jakarta EE.
According to the results, the community wants:
- the platform to support cloud-native development
- a faster pace of innovation on the platform.
Mike Milinkovich, Executive Director of the Eclipse Foundation summarized the future of Jakarta EE in the report’s abstract:
Jakarta EE is the future of cloud-native Java. Jakarta EE’s mission is more frequent releases, lowered barriers to participation, and putting the community back into the platform. It will allow and encourage everyone to participate in an open process that more accurately reflects the needs of the wider community. As it evolves we expect Java innovation from open source communities like Eclipse MicroProfile, that extend the Jakarta EE platform, to be quickly adopted into new versions of the platform to help developers create portable cloud native applications. Jakarta EE represents the best way to drive cloud-native, mission critical applications and build upon the decades of experience of real world deployments and developers.
Very happy to announce that https://t.co/yP4L6P6nZZ is now live!
Many thanks for @chrisguindon and @ericpoir for their great work getting the site live.
Let’s get going @JakartaEE community! pic.twitter.com/xvkj5lKvnX
— Mike Milinkovich (@mmilinkov) April 24, 2018
Jakarta EE Community Survey Results in a nutshell
The results of the community survey show that Java remains the most used programming language (in a business context) and that most enterprise applications are usually built primarily using frameworks based on languages such as Java. Furthermore, 43.27 percent of the respondents said that 80 percent of their applications running in production are based on Java.
One of the most interesting (but not surprising!) highlights is the fact that almost 87 percent of respondents are running Java 8 and just over 45 percent are using Java 7. We’ve talked about Java 8’s popularity in this post.
As far as Java EE is concerned, it seems that stability is the most cited reason for using it, followed by specifications, availability of developers and multiple vendors with compatible implementations. Meanwhile, the most challenging aspect of working with Java EE seems to be large memory requirements, followed by missing technologies and specifications.
Better support for microservices is what over 60 percent of the respondents want for the Jakarta EE platform. Integration with Kubernetes and faster pace of innovation are also highly important.
Jakarta EE, the future of cloud-native Java
Roughly half of survey respondents said that less than 20 percent of their applications are running in the could, which shows that migrating Java applications to the cloud has a long way to go. However, when asked what percentage of their Java systems will be running in the cloud in two years, over 23 percent expect to have over 80 percent of their applications in the cloud.
That said, we’ve barely scratched the surface of Java’s cloud-native future.
What does cloud-native Java mean to Jakarta EE?
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
The Eclipse Foundation expects to see the community working towards better integrations with cloud-native technologies such as Kubernetes and Docker — some integrations must happen at JVM level. Furthermore, they expect the community to collaborate with the OpenJDK and Eclipse OpenJ9 team to provide support at the framework level as these JVM enhancements are made available.
Under its new governance model, the Jakarta EE platform should evolve at a rapid pace, incorporating Java innovations from open source communities like Eclipse MicroProfile into new versions of the platform to help developers create portable cloud-native applications.
Last but not least, Jakarta EE promises faster release and innovation cycles.
Jakarta EE Working Group
Under the Eclipse Foundation, the Jakarta EE Working Group will be based on a self-governing meritocracy that sets all technical agendas and plans. The founding members of the Jakarta EE Working Group are Fujitsu, IBM, Oracle, Lightbend, Payara Systems, Pivotal, Red Hat, Tomitribe and Webtide.
There are four committees comprising the Jakarta EE governance structure — the Steering Committee, the Specification Committee, the Marketing and Brand Committee, and the Enterprise Requirements Committee.
For more information about Jakarta EE, and about joining the Jakarta EE Working Group, please visit www.jakarta.ee.