The pace of Java EE releases has been slowing and has been unable to adapt to the rapid rise of microservices. MicroProfile was created as a means to collaborate with vendors, individuals, and organizations like Java user groups in an open forum, to rapidly bring microservices to traditional Java EE developers. We moved the project to the Eclipse Foundation and have officially renamed it Eclipse MicroProfile. Red Hat is implementing MicroProfile specifications via WildFly Swarm and optimizing it for use on OpenShift.
I held a session at this year’s Red Hat Summit introducing MicroProfile: Optimizing Java EE for a Microservices Architecture and then discussed its current technical and community status, including efforts to collaborate around enterprise Java microservices.
- We addressed the importance of leveraging relevant Java EE technologies.
- We picked a core set of technologies at the beginning, and this set will slowly grow as Java EE evolves (ex: Java API for JSON Binding).
- Customers can leverage existing knowledge and expertise.
- Facilitate customer, vendor, and partner adoption.
- Extending the base Java EE technologies with some new capabilities.
- How we are collaborating in Open Source around this.
- Build a strong community
- Collaborate on specifications
- Encourage multiple implementations
- Standardize technologies when ready
We have laid out the roadmap for the rest of the calendar year and with many microservice related technologies that we want to address across these releases and beyond and have identified WildFly Swarm as our delivery vehicle for MicroProfile.
The Big Takeaway: MicroProfile does not compete with Java EE rather it extends the capabilities of Java EE to better address microservices. Since this is a community project we’re looking for people to get involved in helping us, so come join us!
Whether you are new to Containers or have experience, downloading this cheat sheet can assist you when encountering tasks you haven’t done lately.Last updated: June 30, 2017