My half of the presentation at Devoxx BE 2018 (@DevoxxBE). I give brief histories of both MicroProfile and Jakarta EE, and then discuss ways that the two platforms might come together at some point. The associated recording is here: https://www.youtube.com/watch?v=VqMs6a3nv_0

1. Implementing Microservices with
Jakarta EE and MicroProfile
Ivar Grimstad, Cybercom Sweden, EE4J PMC Lead
Kevin Sutter, IBM, EE4J PMC and MicroProfile Lead

2. Abstract
● https://dvbe18.confinabox.com/talk/PGM-5344/Implementing_Microservices_with_Jakarta_EE_and_Micro
Profile
Java EE was not advancing fast enough. Enterprise Java was being left in the dust in the microservices development
environment. Customers were wondering when Java EE 8 was going to complete and what it was going to contain. And, what
comes after Java EE? The answer is the Eclipse MicroProfile and Eclipse Jakarta EE projects.
In this session we will discuss and demonstrate the MicroProfile programming model for developing microservice
applications. Although MicroProfile is currently based on Java EE technologies, the expectation is that this will evolve to using
the corresponding Jakarta EE technologies. Thus, the synergy between these two Eclipse projects is already starting.
We will also discuss the current state of the Jakarta EE effort. Demonstrating the building and testing of various Jakarta EE
(EE4J) projects is also on the agenda (the exact content to be determined based on the state of the transition efforts).

3. •
•
•
•
…
•

4. @ivar_grimstad
https://github.com/ivargrimstad
https://www.linkedin.com/in/ivargrimstad

5. JavaOne 2015: Java EE – Relevant or Elephant?
5
http://parentrap.org/2014/09/29/easy-parenting-part-iii-the-donts-list/

6. 6
What can we do to
advance microservice
development in the
Enterprise Java space?
-Java EE Community, early 2016
What Happened Next?

7. Characteristics
7
Specs, APIs, TCKs
Community Driven
Lightweight, Iterative
Processes
No Reference
Impls!

8. JavaOne 2016
8
CDI 1.2 JAX-RS 2.0 JSON-P 1.0
MicroProfile 1.0
Announced!
Basic Building Blocks for Microservices

9. CDI 2.0
Fast-forward two years...
9
JAX-RS 2.1 JSON-P 1.1
MicroProfile 2.1
JSON-B 1.0
Fault
Tolerance
1.1
Metrics 1.1
JWT
Propagation
1.1
Health
Check 1.0
Open
Tracing 1.2
Open API
1.0
Rest Client
1.1
Config 1.3
17
Component
Releases!
7 Platform
Releases!
MicroProfile
2.1

10. CDI 2.0
Roadmap...
10
JAX-RS 2.1 JSON-P 1.1
MicroProfile 2.x
JSON-B 1.0
Fault
Tolerance
1.1
Metrics 1.1
JWT
Propagation
1.1
Health
Check 1.0
Open
Tracing 1.2
Open API
1.0
Rest Client
1.1
Config 1.3
Reactive
Operators
1.0
Reactive
Messaging
1.0
Service
Mesh /
ISTIO 1.0
... Component Updates
● Health Check 1.1
● Rest Client 1.2
● Config 1.4
● Metrics 2.0
● Fault Tolerance 1.2
● ...

11. Compatible Implementations!
11
https://wiki.eclipse.org/MicroProfile/Implementation

12. Meanwhile…
12
2017 - 2018

13. 39 EE4J Projects and counting…
● 20% Project Proposal has been posted for community review
● 40% Project committers and resources have been provisioned
● 60% Initial Contribution provided to the Eclipse IP Team
● 80% Initial Contribution Pushed to Git Repository
● 100% Project has engaged in its first Release Review
13
https://www.eclipse.org/ee4j/status.php
Eclipse
Glassfish
5.1-RC1!

14. Eclipse Glassfish Release Schedule
✓Sep 21 -- All code required for GF build contributed.
✓Sep 23 — Eclipse GlassFish builds.
✓Oct 1 -- Java EE 8 CTS testing begins.
✓Oct 22 -- Eclipse GlassFish 5.1-RC1 milestone release.
✓Oct 31 — CI/CD release pipelines completed.
●Nov 12? — Dependencies updated. All projects are released to OSSRH and have dependencies to Eclipse version of other
components.
●Nov 30 -- Release Reviews completed.
●Dec 14 -- Eclipse GlassFish 5.1 release. All Java EE 8 CTS tests passed.
14

15. EE4J CI/CD Progress
15
https://github.com/orgs/eclipse-ee4j/projects/1

16. EE4J Staging Release: APIs
16
https://github.com/orgs/eclipse-ee4j/projects/4

17. EE4J Staging Release: Implementations
17
https://github.com/orgs/eclipse-ee4j/projects/5

18. Jakarta Maven Coordinates
18
https://github.com/orgs/eclipse-ee4j/projects/2

19. Specification Process
19
Specification Process 1.0
● Replacement for JCP Standards Process
● Public Draft Available for Review (Oct 17, 2018)
○ https://docs.google.com/document/d/1ongNU
yGvZPtrcuxA7RQNV2qBESFcAphQbzdk3pU
IQ5s/edit#heading=h.o84um3qls283
○ Comments accepted until Oct 31, 2018
● Guinea Pig Spec Project
○ JNoSQL

20. Additional Work Items in progress...
20
TCK
Compliance
Process
TCK License
Specification
License
...

21. Similarities between MicroProfile and Jakarta EE
● Focused on Microservice and Cloud Native Development
● Desire Agile Development Practices
● Code First Mentality
21

22. Characteristics
22
Specs, APIs, TCKs
Community Driven
Lightweight, Iterative
Processes
No Reference
Impls!

23. Differences between MicroProfile and Jakarta EE
● MicroProfile has an established release process and cycle
○ 7 major releases and 17 component releases in its 2 years of existence
○ Jakarta EE is planning for 1-2 major releases per year (components may have more)
23

24. Differences between MicroProfile and Jakarta EE
● MicroProfile has an established release process and cycle
○ 7 major releases and 17 component releases in its 2 years of existence
○ Jakarta EE is planning for 1-2 major releases per year (components may have more)
● MicroProfile is not a Standards body
○ Jakarta EE needs to replace the JCP
24

25. Differences between MicroProfile and Jakarta EE
● MicroProfile has an established release process and cycle
○ 7 major releases and 17 component releases in its 2 years of existence
○ Jakarta EE is planning for 1-2 major releases per year (components may have more)
● MicroProfile is not a Standards body
○ Jakarta EE needs to replace the JCP
● Jakarta EE brand is valuable and requires stringent compliance testing
○ MicroProfile’s compatibility statements are strictly on the honor system
25

26. Some positive signs...
26
Rest Client 1.x JAX-RS 2.x
???

27. More positive signs...
27
Config JSR
Config
Specification
???

28. Reactive Platform...
28
Reactive
Operators
1.0
Reactive
Messaging
1.0
● https://www.lightbend.com/blog/how-the-microprofile-community-will-shape-jakarta-ee
● Start in MicroProfile with the end goal of becoming part of Jakarta EE
???

29. Other Integrations...
29
Fault Tolerance
● Retry
● Timeout
● CircuitBreaker
● Bulkhead
● Fallback
Fault Tolerance
● Retry
● Timeout
● CircuitBreaker
● Bulkhead
● Fallback
???

30. Jakarta EE Community
30

31. MicroProfile Community
31

32. Both Communities
32

33. 33

34. Anticipated Relationship
34
● Ongoing MicroProfile innovation on top of Jakarta EE, with desired adoption
of foundational technologies into JakartaEE.next

35. Coding Exercises with Ivar...

38. References
● https://openliberty.io/blog/2018/08/16/whats-next-microprofile-jakartaee.html
● https://microprofile.io
○ https://projects.eclipse.org/projects/technology.microprofile
○ https://microprofile.io/projects/
○ https://wiki.eclipse.org/MicroProfile/Implementation
○ https://openliberty.io/guides/
● https://jakarta.ee
○ https://projects.eclipse.org/projects/ee4j/
○ https://github.com/eclipse-ee4j/ee4j
○ https://www.eclipse.org/ee4j/status.php
○ https://github.com/orgs/eclipse-ee4j/projects/1
38

39. MicroProfile Component Backup Material
39

40. Open Tracing
40
URL: https://github.com/eclipse/microprofile-opentracing
Latest Release: https://github.com/eclipse/microprofile-opentracing/releases
Tracing the flow of a request in a distributed environment has always been
challenging but it is even more complex in a microservices architecture, where
requests traverse across not just architectural tiers but also multiple services. The
MicroProfile OpenTracing API provides a standard for instrumenting microservices
for distributed tracing.

41. Open API
41
URL: https://github.com/eclipse/microprofile-open-api
Latest Release: https://github.com/eclipse/microprofile-open-api/releases
OpenAPI provides Java interfaces and programming models which allow Java
developers to natively produce OpenAPI v3 documents from their JAX-RS
applications.

42. Rest Client
42
URL: https://github.com/eclipse/microprofile-rest-client
Latest Release: https://github.com/eclipse/microprofile-rest-client/releases
In the Microservices world, we typically talk REST to other services. While the
JAX-RS specification defines a fluent API for making calls, it is difficult to make it a
true type safe client. MicroProfile Rest Client makes it easy to take an interface
definition and create a JAX-RS client from it.

43. URL: https://github.com/eclipse/microprofile-config
Latest Release: https://github.com/eclipse/microprofile-config/releases
Applications need to be configured based on a running environment. Provides a
standard way to define a hierarchy of config sources from which environmental
config may be injected into a running application.
Config
43
Dev
Test
Prod

44. Fault Tolerance
44
URL: https://github.com/eclipse/microprofile-fault-tolerance
Latest Release: https://github.com/eclipse/microprofile-fault-tolerance/releases
Fault tolerance is about leveraging different strategies to guide the execution and
result of some logic. Defines annotations for container-brokered timeouts, retries,
fallbacks, circuit-breakers and bulkheads. Simplifies the application-handling of
failure in microservice architectures.

45. URL: https://github.com/eclipse/microprofile-metrics
Latest Release: https://github.com/eclipse/microprofile-metrics/releases
To ensure reliable operation of software it is necessary to monitor essential
system parameters. Defines annotations to define metrics and well-known
monitoring endpoints to gather them from.
Metrics
45
Metric
Registry ● Required Base metrics
● Application metrics
● Vendor-specific metrics

46. JWT Propagation
46
URL: https://github.com/eclipse/microprofile-jwt-auth
Latest Release: https://github.com/eclipse/microprofile-jwt-auth/releases
The security requirements that involve microservice architectures are strongly
related with RESTful Security. Defines standard JWT claims so the content of a
JWT token to be used in Java EE RBAC – identifying user principle name and
group names that a container can map to deployment roles.

47. Health Check
47
URL: https://github.com/eclipse/microprofile-health
Latest Release: https://github.com/eclipse/microprofile-health/releases
Health checks are used to probe the state of a computing node from another
machine (i.e. kubernetes service controller) with the primary target being cloud
infrastructure environments where automated processes maintain the state of
computing nodes

48. Reactive Streams Operators (under construction)
48
URL: https://github.com/eclipse/microprofile-reactive-streams
Latest Release:
https://github.com/eclipse/microprofile-reactive-streams/releases
Reactive Streams is an integration SPI - it allows two different libraries that provide asynchronous
streaming to be able to stream data to and from each other.
Reactive Streams is not however designed to be used directly by application developers. The semantics
defined by Reactive Streams are very strict, and are non trivial, particularly in the areas of thread safety,
to implement correctly. Typically, application developers are expected to use third party libraries that
provide the tools necessary to manipulate and control streams. Examples include Akka Streams, RxJava
and Reactor.

49. Reactive Messaging (under construction)
49
URL: https://github.com/eclipse/microprofile-reactive-messaging
Latest Release: N/A
User annotates simple methods…container creates and manages Reactive Streams:

50. Service Mesh / ISTIO (under construction)
50
URL: https://github.com/eclipse/microprofile-service-mesh
Latest Release: N/A
MicroProfile defines programming model for developing cloud-native
microservices. Cloud Native microservices developed with MicroProfile can take
advantage of a Service Mesh by extracting many concerns away from the
development of the microservice itself. It is important for MicroProfile to
understand the capabilities of service mesh, so that MicroProfile can offer
complimentary features for the infrastructure and avoid the conflicts.

51. 51Code One 2018
https://jakarta.ee/news/2018/04/24/jakarta-ee-community-survey/