Voxxed Athens 2018 - Java EE is dead Long live jakarta EE!
1 like217 views
This document discusses the transition from Java EE to Jakarta EE. It provides an overview of the history and evolution of Java EE standards. It then details the formation of Eclipse EE4J and Jakarta EE to take over stewardship of Enterprise Java from Oracle. It outlines the goals of open governance and more agile innovation. Finally, it discusses Red Hat's involvement in projects like WildFly Swarm and EAP Continuous Delivery to support Jakarta EE.
Voxxed Athens 2018 - Java EE is dead Long live jakarta EE!
- 1. Java EE is Dead Long Live Jakarta EE! Dimitris Andreadis Engineering Director Red Hat @dandreadis
- 2. 2016 in a Nutshell Java EE Awakens
- 3. Enterprise Java Standards History 3 J2EE 1.2 J2EE 1.3 J2EE 1.4 Java EE 5 Java EE 6 Java EE 7 Java EE 8 2000 2005 2010 2015 2020 Release Cadence
- 4. JPE J2EE 1.2 J2EE 1.3 J2EE 1.4 Java EE 5 Java EE 6 Dec 2009 Java EE 7 June 2013 Java EE 8 Sept 2017 19 mos 21 mos 25 mos 30 months 42 months 42 months 52 months Time between Java EE releases
- 5. Java EE Guardians (2016)
- 6. Red Hat Summit/DevNation, June 2016 6
- 7. “An open forum to optimize Enterprise Java for a microservices architecture by innovating across multiple implementations and collaborating on common areas of interest with a goal of standardization."
- 9. Java One, Sep 2016 - Java EE 8 replanning 9
- 10. 2017 Review Java EE Strikes Back!
- 11. ● WildFly v11 - Oct 2017 ● JBoss EAP v7.1 - Dec 2017 .1
- 12. Java EE 8 Finalized (Aug/2017) ● Major Updates ○ Servlet 4.0 ○ CDI 2.0 ○ Bean Validation 2.0 ● New APIs ○ JSON-B 1.0 ○ Security 1.0 ● Minor Updates ○ JAX-RS 2.1 ○ JSF 2.3 ○ JSON-P 1.1
- 13. Eclipse MicroProfile Evolution ● MP 1.0 - Sep/16 ● EMP 1.1 - Jul/17 ● EMP 1.2 - Oct/17 ● EMP 1.3 - Jan/18
- 14. 14
- 15. JavaOne 2017 15
- 16. 16
- 17. 17 Eclipse EE4J - Mission ● Create (and evolve) standard EE APIs, RIs and TCKs ○ Using Java EE 8 as baseline ○ Enabling the development of server-side & cloud-native apps ● Come up with a nimble, flexible, open and vendor independent process ○ That evolves the platform in a compatible way ● Build up the new EE4J community of developers, vendors, end-users ○ Enabling competing vendors and tech providers to provide innovations
- 18. Eclipse EE4J - Key Principles ● Opensource ○ Transparency, Meritocracy, Community-Driven ○ Code first, specifications second ○ No Spec Lead having central control of IP ● Compatibility ○ Value of Spec+RI+TCK & Brand Compliance ● Innovation ○ Ensure Java's future as a cloud native development platform ● Agility ○ Just enough process, faster iterations 18
- 19. 2018 & Beyond A New Hope
- 20. Crowdsourced Brand Name to succeed Java EE ● Two options short-listed and put to community vote ○ Jakarta EE ○ Enterprise Profile
- 22. Project Bootstrapping* 1. Open Source Project Proposal has been provided to the Eclipse Foundation 2. Proposal is posted for review 3. Trademark search initiated 4. Trademark search resolved 5. Open Source Project Created 6. Provisioning requested 7. Committers and resources provisioned 8. Initial Contribution provided to the Eclipse IP Team 9. Initial Contribution approved for Check-In 10. Initial Contribution Pushed to Git Repository 11. Initial Contribution approved by the Eclipse IP Team 12. Milestone/snapshot builds are available 13. Project has engaged in its first Release Review *https://www.eclipse.org/ee4j/status.php
- 24. Jakarta EE Directions What Next?
- 25. Java EE - The Good 25*https://jakarta.ee/news/2018/04/24/jakarta-ee-community-survey/
- 27. Java EE - The Bad(ly missing) 27*https://jakarta.ee/news/2018/04/24/jakarta-ee-community-survey/
- 28. Jakarta EE & Eclipse Microprofile ● Eclipse Microprofile APIs can feed into Jakarta EE ○ With faster Eclipse Microprofile acting as incubator for slower Jakarta EE ● Or the two efforts could eventually merge ○ TBD by the Jakarta EE / Microprofile communities Both need to adapt to operate in an increasingly containerized, distributed, proxied, managed, services-based environment 28
- 29. Java EE - The Ugly 29*https://jakarta.ee/news/2018/04/24/jakarta-ee-community-survey/
- 30. Optimized Runtimes for Jakarta EE ● Memory Footprint & Start-up times vastly improved over the years ● We should increase modularization & decoupling of APIs ○ Allows runtime optimizations, turning things off, lazy loading, parallel boot, etc. ● Allow compose-ability in the spec level - bundle only the used APIs ○ How do you test arbitrary combinations of capabilities? ○ Maybe we need to define new profiles 30 https://antoniogoncalves.org/2016/02/02/o-java-ee-7-application-servers-where-art-thou/
- 31. Other Jakarta EE futures ● Support for Reactive Streams & Async APIs ● ServiceMess Integration (Istio) ● New profiles for Mobile & IoT ● Transactions for Microservices? ● Replacements for legacy, like CORBA/IIOP ● Developer productivity improvements 31
- 32. Jakarta EE @ Red Hat How are we involved
- 33. WildFly Swarm (Thorntail) ● Drives our Eclipse Microprofile implementation efforts ● Promoting shared API implementations across projects ● Researching further runtime reduction techniques ● Finalizing support for MP v1.3 ● Looking towards v1.4 & 2.0 33
- 34. WildFly.Next ● Moving to Quarterly timeboxed releases ● Merge only completed features to main branch ● Formalize and enforce topic-branch testing ● Evolve our Kanban continuous feature delivery process ● Emphasis on fast delivery of Java EE 8 and refocus on Jakarta EE
- 35. WF13 Implements all of Java EE 8 ● Released … yesterday!
- 36. WildFly Tentative Roadmap ● WildFly 12, Feb 28, 2018 - DELIVERED ○ EE8 Chunk 1 (Servlet, CDI, JSON-B, JAX-RS, BV, JSF) ○ Continuous feature delivery process ● WildFly 13, May 30, 2018 - DELIVERED ○ EE8 Chunk 2 (JPA, EE Security) ○ New server assembly infrastructure ● WildFly 14, Aug 29, 2018 ○ EE8 Certification ○ Improved package granularity ● WildFly 15, Nov 28, 2018 ○ Jakarta EE?
- 37. JBoss EAP continuous delivery (EAP-CD) ● New EAP delivery stream based off of WildFly quarterly releases ● Targeting primarily OpenShift Cloud based deployments ● Every 3rd or 4th release rolls into a traditional EAP release ● Initially Tech Preview 37https://access.redhat.com/announcements/3411471
- 38. EAP CD - Example Schedule 38
- 39. Get Involved - https://jakarta.ee/ 39
- 40. Shape the Future of Cloud Native Java ● Join the Jakarta EE community ○ https://accounts.eclipse.org/mailing-list/jakarta.ee-community ● Join the Jakarta EE Working Group ○ https://accounts.eclipse.org/mailing-list/jakarta.ee-wg ● Join the Jakarta EE specifications list ○ https://accounts.eclipse.org/mailing-list/jakarta.ee-spec 40