There is a lot of interest in the server-side Java community around using ahead of time (AOT) native compilation provided by Graal Substrate VM to drive down memory usage and cold start times of Java microservices. While these frameworks are technically interesting, the claim is if you spend time rewriting your Jakarta EE applications to utilise these new frameworks, then you will substantially reduce your cloud operational costs. First, by enabling the adoption of a serverless deployment model and second by reducing your containers' memory usage.
Recently we rebranded the Community and Enterprise Editions of the Payara Platform to clarify and strengthen the differences between our Community software and our Enterprise subscriptions for customers.
As a leading contributor to Jakarta EE, we're happy to announce the Eclipse Foundation Jakarta EE 9 Milestone Release and the results of their 2020 Jakarta EE Developer Survey.
The Jakarta EE 9 Milestone Release demonstrates the significant progress made toward the final release later this year, and offers an opportunity for the industry to try the new namespace and start migrating their frameworks.
The 2020 Jakarta EE Developer Survey features responses from thousands of enterprise Java developers around the world, with results showing significant growth of Jakarta EE 8 use and interest in cloud-native Java. The 2020 Jakarta EE Developer Survey results can be downloaded in their entirety here.
We are continuing to change and improve the way we build and report our future platform releases through the introduction of the Open Roadmap.
As part of the new Payara Reef Community Growth Programme initiative, the Open Roadmap aims to collate user feedback clearly and effectively by allowing individuals to comment on any issues via a GitHub project board.
Starting with the latest Payara Platform 201 release, we've made changes to how we build and report our future platform roadmap. We recently introduced the Payara Reef initiative to enhance our communication with the Payara community, and as part of the Reef initiative, we are also introducing the Open Roadmap for the Payara Platform.
The transition of Java EE to the Eclipse Foundation is now complete with the release of the Jakarta EE 8 Platform Specification and the compatible implementations, including Payara Server. The release plan for Jakarta EE 9 is also approved, and will move all the Java EE APIs to the jakarta namespace - providing a future platform for Jakarta EE 10 and beyond.
The approval of the Jakarta EE 9 Release Plan is a great milestone for the Jakarta EE project and a stepping stone towards the evolution of Jakarta EE into a project that meets the community's needs and wants. View the approved Jakarta EE 9 Release Plan here.
It's 6 months since I posted our last roadmap update and the team have been working hard to deliver what we promised at the beginning of the year and have released both our 191 and 192 releases since then. I therefore thought it was a good time to reflect on what we've delivered so far and what we've still got to do.
Today the Eclipse Foundation have announced an Update on Jakarta EE Rights to Java Trademarks which has dramatic implications for the future of Java EE and Jakarta EE. The Payara team have only recently learned about this - so we thought we would blog about how we feel this impacts customers and users of the Payara Platform. We'll also give our thoughts on how Jakarta EE should evolve given the constraints outlined in Mike Milinkovich's blog from the Eclipse Foundation.
Goals of the Payara Platform
Four years ago when I made the first pull request into the Payara repository the team had a number of goals in creating Payara Server. The first was to build a robust, reliable and supported open source application server that could be deployed into production environments and the second was to evolve the Payara Platform to enable Java EE developers to embrace new architectural models and new deployment infrastructure like cloud, IOT and containers. We have achieved many of these goals and driven forward others, and they are still our primary focus as we look towards Payara Platform 6.