Skip to main content

Eclipse MicroProfile, an open forum to collaborate on enterprise Java microservices, would like to announce the release of Eclipse MicroProfile 3.1.

Eclipse MicroProfile 3.1, which builds on the 3.0 version, updates the Metrics, and Health APIs. Like its previous version, MicroProfile 3.1 continues to align itself with Java EE 8 as the foundational programming model for the development of Java microservices.

Note:  Since the recently released Jakarta EE 8 is functionally equivalent to Java EE 8, any Jakarta EE 8 compatible implementation should provide an equivalent foundation for MicroProfile 3.1.

The picture above shows the two APIs that were updated as part of the Eclipse MicroProfile 3.1 release.

  • MicroProfile Metrics 2.1 includes many clarifications, such as metric registry implementations requiring to be thread-safe, gauges requiring to return values that extend java.lang.Number, metrics being omitted by implementations, and private methods in an annotated class not needing metrics. In addition, TCKs were updated to use RestAssured 4.0, the transitive dependency on javax.el-api from the specification build was explicitly excluded, the reusable(boolean) method for MetadataBuilder was added, and information about programmatic creation of metrics (without annotations) was introduced.
  • MicroProfile Health 2.1 introduces the addition of a new method to create responses as well as the addition of a config property to disable implementation Health procedures and improvements to the javadoc. Moreover, TCK enhancements were made, such as the testing of the JSON format, adding a delayed test, and adding test names before each test. Lastly, a duplicate Arquillian import and the EL API transitive dependency were removed.

Benefits of MicroProfile 3.1 are:

  • Continued alignment with Java EE 8 feature subset
  • A richer feature set for Health and Metrics
  • Additional features offering more functionality for implementing enterprise Java microservices
  • Specification clarifications and documentation enhancements
  • Richer integration between MicroProfile APIs
  • All these APIs offer CDI-based and programmatic easy-to-use interfaces
  • Interoperability across different MicroProfile implementations provides users the freedom to select one or combine many MicroProfile implementations in a microservices architecture
  • A thorough set of artifacts for each API, including a Test Compatibility Kit (TCK), Javadoc, PDF and HTML documents for download, API Maven artifact coordinates, Git tag, and downloads (spec and source code)

Eclipse MicroProfile continues to deliver additional value on a regular basis and to successfully evolve with the dynamic involvement of all its community contributors. For example:

Future releases of Eclipse MicroProfile will update existing APIs and/or add new ones. For instance, the following topics are currently under active discussion and may appear in future releases:

Eclipse MicroProfile continues to forge ahead enabling enterprise Java microservices development for Java developers. Whether you’re a coder, end user, designer, or writer and are interested in MicroProfile, we encourage you to join our community members in developing existing specifications, helping with R&D on relevant topics, or even forming a group to cover some innovating new ideas!

For more information on MicroProfile, please visit:

To get your projects kick-started with MicroProfile, please visit:

To get involved in the MicroProfile community, please join our Forum:

For more information on MicroProfile 3.1, please refer to:

For MicroProfile roadmap and upcoming release trains, please go to:

Cesar Saavedra

Author Cesar Saavedra

More posts by Cesar Saavedra

Leave a Reply