At yesterdayâ€™s Eclipse MicroProfile public hangout, we had two major announcements: First, that we have announced the content for the next major MicroProfile 1.1 release and, second, that we have a new MicroProfile logo.
MicroProfile 1.1 content
The original MicroProfile 1.0 release relied on existing Java EE specifications: CDI 1.2, JAX-RS 2.0, and JSON-P 1.0. These three specifications were deemed to provide the absolute minimum programming model for microservices in the Enterprise Java space. Since that original release, the MicroProfile community has been busy defining new specifications that go beyond Java EE. Some of the areas being explored include Configuration, Fault Tolerance, Security (JWT) Propagation, Health Check, Health Metrics, Open Tracing, and Open API (Swagger) integration.
The first MicroProfile component to reach the 1.0 release milestone was the Configuration API. The basic premise of the Configuration specification is to separate the applicationâ€™s configuration data from the application itself. There should be no need to re-build or re-package an application just because the configuration has changed. The application should be able to access or even modify the configuration while in an executing environment.
Just last week, the MicroProfile Configuration component announced their 1.0 release–complete with the specification, API, TCK, and documentation. Implementations that support this Configuration 1.0 definition should be coming shortly, with Apache Geronimo Config and WebSphere Liberty Beta leading the way.
As the MicroProfile community decided to focus on time-boxed deliveries (rather than content-based deliveries), the content for MicroProfile 1.1 was decided by whatâ€™s readyâ€¦ To that end, MicroProfile 1.1 consists of the following technologies:
- Configuration API 1.0
- CDI 1.2
- JAX-RS 2.0
- JSON-P 1.0
New MicroProfile logo
The other major announcement at yesterday’s hangout was our new MicroProfile logo:
Our original logo satisfied our initial needs. But, as we continued to grow, we wanted to ensure that the logo grew with us. We worked as a global team to narrow down the choices and then we decided to let the larger MicroProfile community choose the final design from four finalists (three new logos as well as the original logo). This new logo just barely beat out the original logo, well ahead of the other two proposals.
Finally, just a quick reminder that MicroProfile is an open community and weâ€™re constantly looking for additional participation from vendors, user groups, and individuals. The best way to get started is to take a look at our Google Groups, or jump right into one of our component code repos. Welcome!