Payara
By Payara Services Ltd
Payara Server is a Jakarta EE and MicroProfile-compliant application server derived from the open-source GlassFish project, providing production support, performance improvements, and security patches that GlassFish's community edition…
Definition
Payara Server is a Jakarta EE and MicroProfile-compliant application server derived from the open-source GlassFish project, providing production support, performance improvements, and security patches that GlassFish's community edition does not guarantee on a predictable schedule. It is used to deploy and run enterprise Java applications, including EJB, JSF, and JAX-RS components, in a managed runtime with built-in clustering and monitoring features.
Overview
Payara originated after Oracle scaled back its commercial support commitment to GlassFish following Oracle's acquisition of Sun Microsystems, leaving many enterprises that had built applications on GlassFish without a vendor providing timely patches, security fixes, or a predictable roadmap. Payara Services was founded specifically to fork GlassFish's open-source codebase and offer that continuity — packaging the same Jakarta EE application server technology with an active release cadence, community and paid support tiers, and enterprise features layered on top. Mechanically, Payara Server functions like any Jakarta EE application server: applications packaged as WAR or EAR files are deployed into it, and the server provides the surrounding container services — EJB containers, JSF and JAX-RS runtime support, JPA persistence, JTA transaction management, and CDI dependency injection — that the deployed application relies on without needing to bundle them itself. Payara adds its own monitoring console, health check endpoints, and clustering capabilities on top of the base GlassFish lineage, and offers a separate Payara Micro distribution for running Jakarta EE applications in a more lightweight, container-friendly mode closer to how Helidon or Quarkus operate. Compared to WildFly, Red Hat's Jakarta EE server, Payara occupies a similar market position — both are full application servers competing for organizations that need Jakarta EE compliance with commercial support options — differentiated mainly by their originating vendor, specific tooling, and support contract terms rather than fundamental architecture. Against lighter frameworks like Helidon, Quarkus, or Micronaut, Payara (in its full server form) is a heavier, more traditional application-server deployment model, though Payara Micro narrows that gap for teams wanting Jakarta EE compliance with a smaller footprint. In practice, Payara is chosen by organizations already running Jakarta EE or older Java EE applications that need continued support after GlassFish's commercial backing lapsed, particularly in regulated industries like finance, government, and healthcare where vendor support contracts and prompt security patching are procurement requirements rather than conveniences. Its close lineage to GlassFish also makes migration from GlassFish deployments comparatively straightforward, since much of the deployment descriptor and configuration format carries over directly. The main trade-off with Payara is that it inherits the broader challenges facing traditional Jakarta EE application servers: heavier resource usage and slower startup times than cloud-native frameworks purpose-built for containers, and a smaller mindshare among developers now more often trained on Spring Boot or lightweight microservice frameworks than on full Jakarta EE application servers. Organizations without an existing Jakarta EE investment rarely choose Payara for greenfield projects today, favoring frameworks with faster iteration cycles and native cloud deployment stories instead.
Key Features
- Forked from GlassFish to provide continued Jakarta EE application server support
- Offers commercial support tiers with a predictable patch and release cadence
- Implements Jakarta EE and MicroProfile specifications for enterprise applications
- Provides built-in EJB, JPA, JTA, and CDI container services
- Includes a monitoring console and health check endpoints out of the box
- Supports clustering for high availability across multiple server instances
- Offers Payara Micro as a lighter, container-friendly deployment mode
- Simplifies migration from existing GlassFish deployments due to shared lineage