Payara is Part of the MicroProfile Working Group!

Cloud & Microservices

Payara is part of the MicroProfile Working Group! 

MicroProfile is a set of Enterprise Java APIs and technologies, designed to help with the challenge of building microservices architectures in Java. 

The MicroProfile Working Group develops these APIs in a collaborative process, and is comprised of passionate individuals, and representatives from different vendors and Java User Groups. 

Our CEO and FounderSteve Millidgecommented:Steve bio pic

“We are proud to continuously support and be a part of theMicroProfile Working Group. MicroProfile andJakarta EEare designed to complement each other. Being a part of both Working Groups allows us to fully support, develop and champion cloud native enterprise Java under the Eclipse Foundation. 

Our work in the MicroProfile Working Group also allows us to better implement our own MicroProfile certified products. Payara Platform as a whole is MicroProfile compatible but this is particularly important forPayara Micro,our lightweight microservices platform of choice.  

As the software industry continues to embrace “smaller” deployments, the innovation in the MicroProfile Working Group is step-by-step dismantling the myth that Jakarta EE is only for heavy architectures. Our support for MicroProfile furthers our goal of creating enterprise Java that works for everyone, however you chose to design your applications – monolith, microservices or hybrid.”

MicroProfile-2021

MicroProfileandJakarta EEare both working groups within the Eclipse Foundation. There are a huge range of specifications and APIs that are covered among the two working groups. They share many as a foundation, the CDI, RESTful Web Services, JSON-P, JSON-B, and Annotations. 

On the MicroProfile side, the APIs are basically developed as extensions of Jakarta EE and are specifically for microservices architecture. They are a little more experimental than Jakarta EE. Also, MicroProfile carried Jakarta EE forward from an application server point of view during the transition between Java EE 8 and Jakarta EE 9. Where there were no API changes happening under the Jakarta EE side there were a lot of changes happening on the MicroProfile side. This brings products like Payara Micro and Payara Server up to speed and provided capabilities to provide microservices. 

If you are interested in the relationship between Jakarta EE, MicroProfile and Microservices, you might find these guides useful:

Comments (1)

Post a comment

Your email address will not be published. Required fields are marked *

Payara needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Legal & Privacy Policy.

  1. Anbu

    I thought Payara always part of MicroProfile. congratulations!!

Related Posts

Payara promotional graphic showing transition from Spring to Jakarta EE, including technology logos, a code icon and arrows leading from Spring to Jakarta EE. 6 minutes
Jakarta EE

From Spring Boot To Jakarta EE 11: How Payara Starter Eases The Transition

If you’ve been living in the Spring ecosystem, you’re used to fast project setup. Spring Initializr gives you a […]

Graphic promoting the Jakarta EE Agentic AI Project by Payara Community. The design shows a laptop screen with a central icon of a person wearing headphones and using a laptop, surrounded by sparkles. The background features blue ocean-themed elements with coral and small fish. Logos for Jakarta EE and Payara Community appear at the top. 3 minutes
Community

Announcing the Jakarta Agentic AI Project

Exploring the Future of AI with the Jakarta EE Community At Payara, we’re passionate about pushing the boundaries of […]

Image promoting a Payara blog with an illustration of a document with checkmarks and a magnifying glass. 5 minutes
Jakarta EE

Why Jakarta EE Standards Make Legacy App Modernization Simple

Legacy Java applications built on enterprise standards don’t have to be roadblocks to modernization. When applications follow established specifications […]