1 of 6

CN4J Alliance

Relationship between Jakarta EE and MicroProfile

2 of 6

Jakarta EE

  • Long-standing need for new specifications and revisions to existing specifications
  • Jakarta EE aims to have one major release a year
  • Targets:
    • Monolithic applications
    • Microservices
    • Standalone technology use in Java SE (desktop/command line)
  • Strong backward compatibility focus
  • Jakarta EE aims to provide stability and continuity
  • Specifications can be used independently
  • Enables ecosystem to build on Jakarta EE technologies, including MicroProfile and Spring

3 of 6

MicroProfile

  • Develops new technologies targeted at microservices and cloud-native deployments
  • Depends upon technologies from Jakarta EE
  • Releases several times per year
  • Provides less stringent backward compatibility guarantees
  • Focuses on innovation, velocity instead of stability
    • Technologies, features can be added, modified, dropped, or replaced
  • Not all technologies are a fit for Jakarta EE
    • OpenTelemetry, gRPC, GraphQL, CQRS/Event Sourcing, cloud storage

4 of 6

Proposed Alignment

  • Broad desire for better alignment
  • A significant segment want to see eventual complete convergence
  • Some MicroProfile technologies can transition to Jakarta EE
    • A technology only moves once it is stable enough
    • Moving a technology to Jakarta EE is a collaborative effort
    • Technology namespace changes to the jakarta.* namespace when moved
    • No circular dependencies between MicroProfile and Jakarta EE
    • Configuration, Context Propagation and JWT clearest candidates for transition into Jakarta EE
  • A clear relationship between MicroProfile and Jakarta EE

5 of 6

Jakarta EE Profile Alignment

  • Core Profile
    • Jakarta EE specifications required by MicroProfile
    • Some specifications from MicroProfile
    • CDI Lite
  • Full Profile
    • All Jakarta EE specifications
    • Prune more outdated technologies
  • Web Profile - pruned
    • Not enough Web Profile implementation end-user adoption
    • Core Profile fills target space
  • More focus on independently usable specifications
    • More standalone TCKs, more modularity

6 of 6

Organization

  • Jakarta EE and MicroProfile working groups remain independent
    • There should be reliable communication between them
    • Either the Steering Committee/PMC or similar bodies to align release plans and roadmaps
  • Organization contributing to both should only have to pay one fee