Eclipse Jakarta EE

Eclipse Jakarta EE
Name	Eclipse Jakarta EE
Developer	Eclipse Foundation
Programming language	Java
Operating system	Cross-platform
Platform	Java Platform
License	Eclipse Public License

Eclipse Jakarta EE is an open-source set of specifications for enterprise Java platform components managed by the Eclipse Foundation. It provides standardized APIs and runtime contracts that enable portability across IBM, Red Hat, Oracle Corporation, Payara, and Apache Software Foundation-based implementations. Jakarta EE evolved from enterprise Java efforts originally driven by Sun Microsystems, later influenced by contributions from BEA Systems, GlassFish Community, Tomitribe, and cloud vendors such as Amazon Web Services and Google.

Overview

Jakarta EE defines APIs for building server-side applications using standards that interact with ecosystems like Servlet Container projects and application servers from WildFly, Apache Tomcat, Eclipse GlassFish, Payara Server, and IBM WebSphere. The platform includes specifications for technologies such as Servlet, JavaServer Faces, Java Persistence API, Enterprise JavaBeans, Java Transaction API, and Java Message Service. Jakarta EE aligns with other industry standards and frameworks including MicroProfile, Spring Framework, Hibernate, and cloud-native initiatives from Cloud Native Computing Foundation. Major vendors such as Microsoft and Oracle Corporation contribute to runtime integration for platforms like Kubernetes, OpenShift, and Docker orchestration.

History and Evolution

Jakarta EE originated from the transition of enterprise Java stewardship from Oracle Corporation to the Eclipse Foundation following community and vendor discussions involving Java Community Process, Java Specification Request, and stakeholders such as IBM, Red Hat, Payara, Eclipse GlassFish contributors, and the Apache Software Foundation. The rebranding and namespace change required coordination with projects like GlassFish and legal work tied to trademarks held by Oracle Corporation and historical work from Sun Microsystems. Over time Jakarta EE incorporated community-driven efforts from Eclipse MicroProfile, collaboration with cloud providers like Amazon Web Services and Google, and influence from open-source governance models exemplified by Linux Foundation projects.

Architecture and Specifications

The Jakarta EE architecture is modular and layered, with core components providing web, persistence, transaction, and messaging services. Key specifications include Jakarta Servlet, Jakarta Server Faces, Jakarta Persistence, Jakarta Enterprise Beans, Jakarta Transactions, Jakarta Messaging, and security specs influenced by standards from OWASP and integration patterns from Apache Camel. The platform coordinates with tools and languages such as Maven, Gradle, JUnit, Arquillian, and CI/CD systems from Jenkins and GitHub Actions. Jakarta EE’s specification process engages contributors from organizations including Red Hat, IBM, Oracle Corporation, Payara, and Tomitribe, paralleling governance models seen in Apache Software Foundation projects and Eclipse Foundation incubator initiatives.

Implementations and Ecosystem

Multiple commercial and community implementations provide Jakarta EE runtimes: Eclipse GlassFish, Payara Server, WildFly, Apache Tomcat with added components, and IBM WebSphere Liberty. Vendors such as Red Hat, IBM, Oracle Corporation, Fujitsu, and Tencent offer support and integrations. Tooling vendors and projects like IntelliJ IDEA, Eclipse IDE, NetBeans, Maven Central, Gradle Plugin Portal, and testing suites from JUnit and TestNG support Jakarta EE development. Cloud and container platforms including Kubernetes, OpenShift, Docker, Google Cloud Platform, Amazon Web Services, and Microsoft Azure host Jakarta EE applications with service meshes from Istio and observability stacks like Prometheus and Grafana.

Governance and Community

Jakarta EE is governed by the Eclipse Foundation through a specification process involving a wide array of corporate and community members including Red Hat, IBM, Oracle Corporation, Payara, Tomitribe, Google, and Microsoft. Community efforts intersect with standards bodies and initiatives such as the Java Community Process and projects under the Cloud Native Computing Foundation. Working groups, specification leads, and project committees often include contributors from Apache Software Foundation projects, commercial vendors like Fujitsu and Tencent, and research institutions. Outreach, conferences, and collaboration occur at events like JavaOne, Devoxx, EclipseCon, QCon, and regional meetups.

Use Cases and Industry Adoption

Jakarta EE is used for enterprise web applications, microservices, and backend systems in industries supported by vendors such as IBM, Red Hat, Oracle Corporation, Payara, and cloud providers including Amazon Web Services and Google. Sectors adopting Jakarta EE include finance institutions using platforms from Fujitsu and IBM WebSphere, telecommunications operators leveraging Kubernetes and OpenShift integrations, and government agencies deploying secure applications with tools from OWASP and identity integrations like Keycloak. Jakarta EE’s compatibility encourages migration from legacy Java EE deployments on application servers such as GlassFish and JBoss to modern containerized environments supported by Docker and orchestration from Kubernetes.

Criticisms and Challenges

Critics cite the complexity of maintaining broad specification sets across stakeholders like Oracle Corporation, Red Hat, and IBM and the challenges of namespace transitions originating from Sun Microsystems ownership. Interoperability efforts require coordination with ecosystems managed by Apache Software Foundation projects and cloud vendors including Amazon Web Services and Google, sometimes slowing specification cadence. Competition from frameworks such as Spring Framework and microservice-focused initiatives like Spring Boot and Eclipse MicroProfile raises concerns about perceived heaviness and adoption speed among startups and cloud-native teams. Ensuring security compliance with guidance from OWASP and meeting performance expectations on platforms like Kubernetes and OpenShift remain ongoing technical and operational priorities.

Category:Java platform