LLMpediaThe first transparent, open encyclopedia generated by LLMs

Payara Micro

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: MicroProfile Hop 4
Expansion Funnel Raw 76 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted76
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Payara Micro
NamePayara Micro
DeveloperPayara Services Ltd
Released2016
Programming languageJava
Operating systemCross-platform
GenreApplication server, Java EE, Jakarta EE
LicenseOpen-source

Payara Micro Payara Micro is a lightweight, cloud-native runtime for executing Jakarta EE and Java EE applications in microservices and containerized environments. It targets developers and operators who use Oracle Corporation's Java Platform, Enterprise Edition lineage alongside ecosystems around Eclipse Foundation projects, GlassFish derivatives, and cloud platforms such as Kubernetes and OpenShift. Payara Micro emphasizes fast startup, minimal footprint, and integration with orchestration systems like Docker and Apache Maven-based build pipelines.

Overview

Payara Micro emerged to address needs for running enterprise Java applications on platforms including Amazon Web Services, Google Cloud Platform, and Microsoft Azure. It provides a runtime alternative to traditional application servers such as JBoss EAP, WebLogic Server, and IBM WebSphere Application Server, while interoperating with frameworks and tools like Spring Framework (for hybrid deployments), Hibernate ORM, and Eclipse MicroProfile. The project is associated with Payara Services Ltd, which offers commercial support and services for enterprise deployments similar to how Red Hat supports WildFly.

Architecture and Components

The architecture centers on a single executable JAR model that packages a reduced-profile runtime plus application artifacts. Core components derive from the GlassFish codebase and interact with subsystems such as the Grizzly NIO framework for HTTP handling, the Weld CDI implementation for dependency injection, and the Jakarta RESTful Web Services stack for JAX-RS endpoints. Runtime services include an embedded web container, transaction management powered by implementations compatible with Java Transaction API, and persistent-data integration via connectors for Jakarta Persistence API and JDBC drivers for databases like PostgreSQL, MySQL, and Oracle Database. Observability is provided through integrations with Prometheus exporters and Jaeger tracing for distributed systems.

Features and Capabilities

Payara Micro supports hot-deploy and auto-redeployment workflows commonly used with Apache Ant and Maven. It implements MicroProfile specifications such as MicroProfile Config, MicroProfile Health, MicroProfile Metrics, and MicroProfile Fault Tolerance to enable resilient, configurable microservices compatible with standards favored by enterprises including Netflix-style patterns. The runtime includes clustering features through technologies analogous to those in Hazelcast and supports logging integration with Logback and Log4j. Management capabilities include dynamic configuration, centralized administration options that complement orchestration tools like Helm, and tooling for blue-green or canary deployments used by organizations like Spotify and Netflix.

Deployment and Operations

Designed for containerized deployment, Payara Micro runs as a self-contained artifact in Docker containers orchestrated by Kubernetes or Red Hat OpenShift. CI/CD pipelines often use Jenkins, GitLab CI/CD, or CircleCI to build and push images to registries such as Docker Hub or GitHub Packages. Runtime lifecycle hooks and health endpoints integrate with platform controllers for liveness and readiness probes used by Istio service meshes and Linkerd. For stateful requirements, operators combine Payara Micro with storage solutions like Amazon EBS, Google Cloud Storage, or Ceph.

Performance and Scalability

Payara Micro targets low-latency startup and efficient memory usage to improve horizontal scaling economics on cloud infrastructure provided by Amazon EC2, Google Compute Engine, and Microsoft Azure Virtual Machines. Performance tuning leverages JVM options associated with OpenJDK distributions, garbage collectors like G1 GC and Z Garbage Collector, and monitoring stacks that include Grafana dashboards fed by Prometheus metrics. Load-testing often uses tools such as Apache JMeter and Gatling to validate response times and throughput under patterns observed in services operated by companies like Airbnb and Uber.

Security and Compliance

Security features align with Jakarta EE security models and include integrations for OAuth2 and OpenID Connect providers such as Keycloak and Okta. Transport-layer security is enabled via TLS configurations that reference certificate management solutions including Let's Encrypt and secrets management systems like HashiCorp Vault. Payara Micro supports role-based access control and audit logging compatible with compliance regimes enforced in enterprises similar to PCI DSS and GDPR, and is used with identity providers common to organizations like Salesforce and Microsoft.

History and Development

The product originated when contributors and maintainers of the GlassFish ecosystem formed Payara Services Ltd to continue evolution of a lightweight GlassFish-derived runtime for cloud-native Java. Initial public releases followed trends from the rise of Docker containers and the adoption of Kubernetes for orchestration, and development has included alignment with the transition from Java EE to Jakarta EE under the Eclipse Foundation. Commercial support, bugfix streams, and enterprise features have been delivered alongside community updates, mirroring business models used by vendors such as Red Hat and Confluent.

Category:Java enterprise platform