Learn about Enterprise Java micro services and Eclipse MicroProfile, what it is, its evolution, how Red Hat implements it and delivers it.

1. Eclipse MicroProfile
Enterprise Java microservices specification
Cesar Saavedra
Senior Principal Product Marketing Manager - EAP & MicroProfile
@cesar_saavedr
October 2017

2. 2
● Eclipse MicroProfile is an open-source community specification for
Enterprise Java microservices
● A community of individuals, organizations, and vendors
collaborating within an open source (Eclipse) project to bring
microservices to the Enterprise Java community
What is Eclipse MicroProfile?

3. 3
Community - individuals, organizations, vendors
And Growing ...
3

4. 4
Java Community Process
Standards organization
Large multi-feature releases
Spec Lead controls pace
Eclipse MicroProfile
(Open Source) Project
Incremental feature release
Community controls pace
Innovation vs. Standardization

5. 5
Time between Java EE releases
JPE J2EE 1.2 J2EE 1.3 J2EE 1.4 Java EE 5 Java EE 6 Java EE 7 Java EE 8
19 mos
21 mos
25 mos
30 months
42 months
42 months
52 months

6. 6
Accelerating Adoption of Microservices
Time
8 9
1.0
1.1
2.0
2.1
2.2

7. 7
MicroProfile 1.0 (Sep, 2016)
MicroProfile 1.0
JAX-RS 2.0JSON-P 1.0CDI 1.2

8. 8
Eclipse MicroProfile 1.1 (August, 2017)
MicroProfile 1.1
= New
= No change from last release
JAX-RS 2.0JSON-P 1.0CDI 1.2
Config 1.0

9. 9
Applications need to be configured based on a running environment. It
must be possible to modify configuration data from outside an
application so that the application itself does not need to be repackaged
Configuration 1.0
Dev
Test
Prod

10. 10
Multiple projects directly influenced this proposal and acted as basis for
this API, such as:
● DeltaSpike Config (http://deltaspike.apache.org/documentation/configuration.html)
● Extracted parts of DeltaSpike Config (https://github.com/struberg/javaConfig/)
● Apache Tamaya (http://tamaya.incubator.apache.org/)
● Sabot, merged into Tamaya (https://tomitribe.io/p/sabot)
Current implementations:
● Apache Geronimo Config
● WebSphere Liberty (Beta)
Configuration 1.0 - Influence and Implementations

11. 11
● MicroProfile Configuration 1.0 was introduced as a Java
Specification Request to the Java Community Process Executive
Committee meeting on August 2017
● At the September 2017 EC meeting, Eclipse will formally propose
the Configuration JSR for discussion and vote
● This fulfills one of the goals of Eclipse MicroProfile to serve as an
innovation open source project to the Java community in regards to
Enterprise Java microservices
Configuration 1.0 - as a JSR

12. 12
● Contexts and Dependency Injection (CDI 1.2)
● Java API for RESTful Web Services (JAX-RS 2.0)
● Java API for JSON Processing (JSON-P 1.0)
● Eclipse MicroProfile Specification PDF document
● Config 1.0:
o Technology Compatibility Kit (TCK)
o Javadocs
o Config 1.0 Specification PDF document
o API Maven artifact coordinates
o Git tag
Eclipse MicroProfile 1.1 release content

13. 13
Eclipse MicroProfile 1.2 (Q4 CY2017)
MicroProfile 1.2
= New
= No change from last release
JAX-RS 2.0JSON-P 1.0CDI 1.2
Config 1.1
Fault
Tolerance
1.0
JWT
Propagation
1.0
Health
Check 1.0
Metrics 1.0

14. Metrics 1.0
To ensure reliable operation of software it is necessary to monitor essential
system parameters. Metrics adds well-known monitoring endpoints and metrics for
each process
14
Metric Registry
Required Base metrics
Application metrics
Vendor-specific metrics

15. Metrics 1.0 - Influence
Multiple projects directly influenced this proposal and acted as basis for this API,
such as:
● DropWizard Metrics 3.2.3
● CDI extension for DropWizard Metrics 1.4.0
● UoM, JSR 363
● Jolokia JMX-HTTP bridge
● Metrics 2.0
Metrics are different from Health Checks, which are primarily targeted at a quick
yes/no response to the question "Is my application still running ok?".
15

16. Health Check 1.0
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
16

17. Health Check 1.0 - Goals
● MUST be compatibility with well known cloud platforms
(i.e. http://kubernetes.io/docs/user-guide/liveness/)
● MUST be appropriate for machine-to-machine
communication
● SHOULD give enough information for a human
administrator
17

18. Fault Tolerance 1.0
Fault tolerance is about leveraging different strategies to guide the execution and
result of some logic. Retry policies, bulkheads, and circuit breakers are popular
concepts in this area. They dictate whether and when executions should take
place, and fallbacks offer an alternative result when an execution does not
complete successfully
18

19. Fault Tolerance 1.0 - Influence and goal
Multiple projects directly influenced this proposal and acted as basis for this API,
such as:
● Hystrix
● Failsafe
Goal:
● Separate the responsibility of executing logic (Runnables/Callables/etc) from
guiding when execution should take place (through retry policies, bulkheads,
circuit breakers)
19

20. JWT Propagation 1.0
The security requirements that involve microservice architectures are strongly
related with RESTful Security. In a RESTful architecture style, services are usually
stateless and any security state associated with a client is sent to the target
service on every request in order to allow services to re-create a security context
for the caller and perform both authentication and authorization checks
20

21. JWT Propagation 1.0 - Influence and goals
Multiple projects/standards directly influenced this proposal and acted as basis for this API, such as:
● OAuth2
● OpenID Connect(OIDC), and
● JSON Web Tokens(JWT)
Goal:
● One of the main strategies to propagate the security state from clients to services or even from
services to services involves the use of security tokens.
● For RESTful based microservices, security tokens offer a very lightweight and interoperable way to
propagate identities across different services.
21

22. Eclipse MicroProfile 1.2 - release content
● Contexts and Dependency Injection (CDI 1.2)
● Java API for RESTful Web Services (JAX-RS 2.0)
● Java API for JSON Processing (JSON-P 1.0)
● Eclipse MicroProfile 1.2 Specification PDF document
22
Config 1.1 Health Check 1.0 Metrics 1.0 Fault Tolerance 1.0 JWT Propagation 1.0
- Product page
- Technology
Compatibility Kit
(TCK)
- Javadocs
- Spec PDF doc
- API Maven artifact
coordinates
- Git tag
- Product page
- Technology
Compatibility Kit
(TCK)
- Javadocs
- Spec PDF doc
- API Maven artifact
coordinates
- Git tag
- Product page
- Technology
Compatibility Kit
(TCK)
- Javadocs
- Spec PDF doc
- API Maven artifact
coordinates
- Git tag
- Product page
- Technology
Compatibility Kit
(TCK)
- Javadocs
- Spec PDF doc
- API Maven artifact
coordinates
- Git tag
- Product page
- Technology
Compatibility Kit
(TCK)
- Javadocs
- Spec PDF doc
- API Maven artifact
coordinates
- Git tag

23. Eclipse MicroProfile 1.3 (Q4 CY2017?)
MicroProfile 1.x
= New
= No change from last release
JAX-RS 2.0JSON-P 1.0CDI 1.2 Config 1.1
Fault
Tolerance
1.0
JWT
Propagation
1.0
Health
Check 1.0
Metrics 1.0
Open
Tracing 1.0
Open API
1.0
Roadmap

24. Eclipse MicroProfile 2.0 (Q4 CY2017?)
MicroProfile 2.0
= New
= No change from last release
JAX-RS 2.1JSON-P 1.1CDI 2.0 Config 1.1
Fault
Tolerance
1.0
JWT
Propagation
1.0
Health
Check 1.0
Metrics 1.0
Open
Tracing 1.0
Open API
1.0
JSON-B 1.0
Roadmap

25. 25
Eclipse MicroProfile vendor implementations
Not an exhaustive list
Open Source Open Source Open SourceOpen Source

26. 26
The Conference Application
Integrating MicroProfile implementations across different vendors

27. 27
MicroProfile within Red Hat ecosystem
Building APIs, orchestrations, BPM processes, etc.

28. OPENSHIFT
APPLICATION RUNTIMES
Application runtimes and a prescriptive developer
experience for organizations that are moving beyond
Enterprise Java and embracing cloud-native application
development.
28

29. 29
Red Hat OpenShift Application Runtimes (RHOAR)
Providing a key set of integrated and curated runtimes, frameworks and developer tools
INTEGRATED AND MANAGED RUNTIMES
(Container images and Maven artifacts)
JAVA EE
(Red Hat JBoss®
EAP)
MICROPROFIL
E
(WildFly
Swarm)
RED HAT
OPENSHIFT SERVICES
REACTIVE
(vert.x)
NODE.JS
APACHE
TOMCAT
CERTIFIED FRAMEWORKS
(Maven artifacts)
SPRING BOOT /
CLOUD
NETFLIX OSS
Ribbon
OpenShift.io
(Developer
SaaS)
Generators
IDE
etc.
Management
APM
Metrics
Service
discovery
Config.
Logging
Health
check
Load
balancing
CI/CDSSOMessaging IMDG API Mgmt
NETFLIX OSS
Hystrix
...

30. 30
● RHOAR includes both MicroProfile and Spring Boot/Cloud
● MicroProfile is an open source project truly owned and managed by
the community whereas Spring is really managed/run by a single
vendor, Pivotal
● We fully support MicroProfile on RHOAR and certify Spring
Boot/Cloud
MicroProfile and Spring Boot

31. 31
● It’s an open community-based specification
● Open-source implementation in WildFly Swarm
● Fast innovation, constant improvement, and introduction of new
capabilities in specification and implementation
● Little to no learning curve for your experienced Java and Java EE
developers
● Delivered in a container-based polyglot platform, RHOAR
Advantages of using Eclipse MicroProfile

32. Java EE going to The Eclipse Foundation
● Strong experience and involvement with Java EE and related
technologies
● Vendor-friendly, vendor-neutral
● It will help Oracle:
○ transition Java EE rapidly
○ create community-friendly processes for evolving the platform,
and
○ leverage complementary projects such as MicroProfile

33. 33
● Java EE & GlassFish technologies, including RIs, TCKs &
documentation
● Build compatible implementation that passes Java EE 8 TCKs.
● Existing javax package names & “Java” in JSR names remain
● Define branding strategy (new name for Java EE)
● Define process for existing specs to evolve & new specs
● Recruit and enable developers, community members & vendors, to
sponsor platform technologies to bring platform forward, including the
potential incorporation of Eclipse MicroProfile into the platform
What assets are moving over to Eclipse
Oracle’s intention - plans are always subject to change

34. 34
Java EE move to open source foundation
Good news for developers, organizations, and Red Hat
will have a channel
for their innovations,
not owned by any
single company
Java will continue to
innovate for their
needs as they move
apps to containers
We support Java EE
in EAP, as well as in
RHOAR and EAP on
OpenShift
Java developers Enterprises Red Hat

35. Benefits to customers
The future is looking very bright
● COMMUNITY POWERED, not vendor controlled
○ new Java EE functionality that results from community collaboration and market
needs
● FASTER releases
○ new Java EE functionality delivered faster to customers and developers
● EVOLUTION, not revolution
○ continued use of Java EE to develop modern architectures and applications, and
○ cost savings from not having to re-train your developers on another framework

36. 36
● Check out the MicroProfile.io website
● Check out the WildFly Swarm website
● Check out our RHOAR announcement
● Check out the value of a Red Hat Subscription
● Contact your Red Hat account executive if you would like to
participate in our Tech Program for RHOAR
Call to action

37. For help getting started, visit
http://brand.redhat.com/applications/presentations
For more information on how to use this template within Google Slides,
view this step-by-step guide.