Jakarta EE

Jakarta EE Jakarta EE is an enterprise-grade platform for building and deploying large-scale server-side Java (programming language) applications. Originating from a long lineage of specifications and reference implementations, it provides a standardized set of APIs and profiles for transactional, web, messaging, and persistence capabilities used by corporations, cloud providers, and systems integrators such as Oracle Corporation, Red Hat, and IBM. The platform is governed and evolved through a collaborative open-source process hosted by the Eclipse Foundation, interacting with vendors, academic institutions, and standards-oriented organizations like Apache Software Foundation and Linux Foundation.

History

Jakarta EE's roots trace back to the enterprise specification efforts maintained by Sun Microsystems and later Oracle Corporation under the name Java Platform, Enterprise Edition. Key milestones include the release cycles driven by the Java Community Process and the corporate transitions surrounding Oracle's acquisition of Sun Microsystems. The transfer of the enterprise specifications to the Eclipse Foundation marked a governance and trademark shift that followed negotiations involving legal and community stakeholders, echoing patterns seen in other technology migrations such as the move of Mozilla Firefox to community-led stewardship. Early community discussions and technical working groups involved participants from IBM, Red Hat, Payara Services Ltd., Tomitribe, Fujitsu, and academic collaborators associated with institutions similar to Massachusetts Institute of Technology. The platform's evolution has been influenced by other ecosystem efforts including Spring Framework innovations and cloud-native trends promoted by Cloud Native Computing Foundation projects.

Technology and Specifications

Jakarta EE defines a set of specification documents and Technology Compatibility Kits that prescribe behavior for APIs implemented by vendors. Core specification areas include web technologies historically related to Jakarta Servlet, persistence aligned with Jakarta Persistence, and messaging consistent with Jakarta Messaging concepts. Transactional semantics reflect influences from Java Transaction API work and standards analogous to those produced by Object Management Group. Security specifications draw on patterns seen in OAuth 2.0 and OpenID Connect integrations championed by identity providers like Okta and ForgeRock. The platform maintains backward compatibility considerations informed by prior releases of Java SE and interacts with build and dependency tools from projects such as Maven and Gradle while integrating with container runtimes and orchestration platforms exemplified by Docker and Kubernetes.

Architecture and Components

Jakarta EE is organized around modular specifications that constitute the platform architecture, enabling implementations to assemble profiles or full stacks. Core components include web layer APIs comparable to Jakarta Faces and Jakarta Server Pages; persistence and object-relational mapping via Jakarta Persistence; dependency injection inspired by patterns from Contexts and Dependency Injection for Java implementations; and enterprise integration points such as connectors similar to Java EE Connector Architecture. Messaging, batch processing, and scheduling correspond to APIs influenced by Jakarta Messaging and Jakarta Batch traditions. The architecture supports standardized deployment descriptors and runtime management models compatible with administration consoles and monitoring systems produced by vendors like Oracle Corporation and Red Hat. Platform extensions and microprofile-style adaptations have been informed by efforts originating at organizations such as Eclipse MicroProfile and projects affiliated with Apache Software Foundation subprojects.

Implementations and Ecosystem

A diverse set of commercial and open-source application server implementations provide compatibility with the Jakarta EE specifications. Notable implementers include vendor products and projects from Red Hat (downstream of WildFly lineage), Payara Services Ltd. (Payara Server), and initiatives connected to Eclipse GlassFish stewardship. Commercial distributions and cloud offerings from IBM and Oracle Corporation have produced certified runtimes, while cloud-native-focused platforms integrate Jakarta EE components into service meshes and platform-as-a-service solutions exemplified by providers like Amazon Web Services and Google Cloud Platform. Tooling and frameworks that complement implementations include ecosystem projects such as Apache Tomcat, Spring Framework adapters, build integrations from Maven Central artifact streams, and observability integrations tied to vendors like New Relic and Dynatrace. The ecosystem also features testing frameworks influenced by work from JUnit and continuous delivery pipelines using systems such as Jenkins and GitLab CI/CD.

Governance and Community

Governance is administered by the Eclipse Foundation through working groups, specification committees, and a formal compatibility process that involves corporate members and individual contributors from organizations including Red Hat, IBM, Payara Services Ltd., Fujitsu, and Tomitribe. The community model emphasizes open mailing lists, public issue trackers, and specification review cycles comparable to models used by W3C and IETF. Contributor agreements and intellectual property policies reflect practices akin to other foundation-hosted projects, while outreach and education efforts engage conferences and user groups like JavaOne-related events, regional meetups, and academic symposiums at institutions such as Stanford University.

Adoption and Use Cases

Jakarta EE is widely adopted across industries for mission-critical applications in banking, telecommunications, healthcare, and government systems, implemented by financial institutions similar to HSBC and telecommunications operators with infrastructures akin to AT&T or Verizon Communications. Use cases include high-throughput transaction processing, enterprise resource planning integrations connecting to systems from vendors like SAP SE, and backend services for large e-commerce platforms comparable to Amazon.com. The platform is leveraged for modernization projects migrating legacy Java Platform, Enterprise Edition applications to cloud-native deployments on orchestration platforms such as Kubernetes while retaining compatibility with existing middleware from vendors like Oracle Corporation and IBM. Category:Java platform