Generated by GPT-5-mini| Eclipse MicroProfile | |
|---|---|
| Name | Eclipse MicroProfile |
| Developer | Eclipse Foundation |
| Released | 2016 |
| Programming language | Java |
| Operating system | Cross-platform |
| License | Eclipse Public License |
Eclipse MicroProfile Eclipse MicroProfile is a set of specifications for building microservices using Java SE technologies targeted at cloud-native environments. It complements Jakarta EE and aligns with architectures promoted by Cloud Native Computing Foundation, Docker, Kubernetes, and cloud providers such as Amazon Web Services, Microsoft Azure, and Google Cloud Platform. The project is governed under the Eclipse Foundation umbrella and is used alongside frameworks like Spring Framework, Quarkus, Helidon, and WildFly.
MicroProfile defines a coordinated set of APIs to address configuration, fault tolerance, metrics, health checks, and more for microservices running on Java Virtual Machine platforms. The initiative was initiated by vendors including Red Hat, IBM, Payara, Tomitribe, and Oracle engineers who sought to harmonize practices popularized by projects such as Eclipse Vert.x, Dropwizard, and Spring Boot. Stakeholders include enterprises using SAP SE, Deutsche Bank, HSBC, and platforms provided by OpenShift and Cloud Foundry. MicroProfile interoperates with build tools like Maven, Gradle, and Apache Ant and CI/CD systems such as Jenkins, GitLab CI, and Travis CI.
The MicroProfile architecture organizes functionality into modular specifications that can be combined to compose a complete microservices stack on Java EE and Jakarta EE runtimes. Core specifications include Configuration, Fault Tolerance, Metrics, Health, and OpenAPI; complementary specs encompass JWT Propagation, Reactive Streams Operators, Rest Client, and Context Propagation. These specifications integrate with standards such as JSON Web Token, OpenAPI Specification, HTTP/2, and gRPC and align with observability systems like Prometheus and OpenTracing and tracing projects such as Jaeger and Zipkin. Security and identity are addressed via JWT and integrations with OAuth 2.0, OpenID Connect, and enterprise identity providers like Okta, Keycloak, and Microsoft Active Directory.
Multiple runtime and framework projects implement MicroProfile specs, enabling portability across vendors. Notable implementations include Payara Server, WildFly Swarm (Thorntail), KumuluzEE, OpenLiberty, Quarkus adapters, and Helidon. Cloud-native platforms integrating MicroProfile implementations include Red Hat OpenShift, Google Kubernetes Engine, Amazon EKS, and Azure Kubernetes Service. Tooling and ecosystem projects include integrations with Eclipse Che, Eclipse Jakarta EE, JBoss, NetBeans, and IntelliJ IDEA. Observability and diagnostics are supported via adapters to Grafana, Prometheus, ELK Stack, Fluentd, and Splunk. Service mesh and networking integrations reference Istio, Linkerd, Envoy, and Consul. Message, event, and streaming integrations align with Apache Kafka, RabbitMQ, ActiveMQ, and Apache Pulsar.
Organizations use MicroProfile for developing microservices in sectors like finance, healthcare, telecommunications, and e-commerce at companies such as Goldman Sachs, JPMorgan Chase, UnitedHealth Group, Siemens, Ericsson, and Alibaba Group. Use cases include API backends, event-driven architectures leveraging Apache Kafka and RabbitMQ, serverless functions executed on AWS Lambda and Azure Functions adapters, and edge computing deployments on Raspberry Pi clusters and ARM-based instances provided by AWS Graviton. Integration scenarios pair MicroProfile services with databases such as PostgreSQL, MySQL, MongoDB, Oracle Database, and Microsoft SQL Server, and with caching systems like Redis and Hazelcast. Monitoring and SRE workflows employ Prometheus alerting, Grafana dashboards, and incident management via PagerDuty and ServiceNow.
MicroProfile began as a vendor-led effort in 2016 to create a focused set of APIs for microservices in the Java ecosystem, with founding contributors from Red Hat, IBM, Tomitribe, Payara, and Oracle. The project moved to the Eclipse Foundation to benefit from neutral governance, following a model similar to how Jakarta EE evolved from Java EE stewardship. Governance is overseen by the MicroProfile Working Group under the Eclipse Foundation with contributions from companies such as Canonical, Fujitsu, Huawei, WSO2, and Lightbend. Release processes and compatibility are coordinated through specification process documents and community groups, and the project tracks advances in cloud-native patterns promoted by the Cloud Native Computing Foundation and standards bodies including the IETF and W3C.