Payara

Payara
Name	Payara Server
Developer	Payara Services Ltd.
Initial release	2014
Programming language	Java (programming language)
Operating system	Cross-platform
Platform	Java Virtual Machine
License	GNU General Public License / commercial

Payara is an open-source, enterprise-grade application server derived from GlassFish and tailored for production deployments of Jakarta EE and Java EE applications. It targets organizations and developers seeking a supported runtime for standards such as Servlet, JPA, JAX-RS, and EJB, while offering commercial support, extended maintenance, and enterprise features. Payara integrates with orchestration and observability tooling used alongside Kubernetes (software), Docker (software), Prometheus, and Grafana to enable cloud-native Java deployments.

History

Payara emerged when contributors and maintainers of GlassFish sought a sustainable commercial support pathway after stewardship transitions involving Oracle Corporation and the Eclipse Foundation. Its formation in the mid-2010s responded to enterprise demand for long-term stability similar to vendor-supported runtimes like Red Hat JBoss Enterprise Application Platform and IBM WebSphere Application Server. Over successive releases, Payara incorporated bug fixes and security patches originally addressed in GlassFish while adding production-focused capabilities paralleling features in Apache Tomcat ecosystems and commercial offerings from Oracle Corporation and Microsoft Azure partners.

Architecture and Components

The core runtime is a fork of GlassFish's modular architecture built on the Java Virtual Machine and integrates a lightweight OSGi-style service model inspired by modular platforms such as Eclipse (software). Major components include a servlet container comparable to Apache Tomcat, a persistence layer leveraging EclipseLink, a web services stack interoperable with Apache CXF and JAX-WS, and a messaging subsystem compatible with Java Message Service. Management and administration rely on an HTTP-based management console and a CLI similar in function to management tools in JBoss AS and WebLogic Server. For clustering and high availability, Payara implements mechanisms analogous to session replication approaches used by HAProxy and Nginx, and integrates with service discovery patterns common to Consul (software) and etcd.

Editions and Licensing

Payara is offered in multiple editions to accommodate different organizational needs, paralleling models used by Red Hat and Oracle Corporation. A community edition provides source code and ongoing development akin to many Apache Software Foundation projects, while commercially supported editions deliver extended maintenance, security backports, and SLA-backed support similar to products from IBM and Red Hat. Licensing mixes open-source licenses—for example, components with GNU General Public License-compatible terms—and commercial subscription agreements for enterprise services. This dual model echoes the strategies of vendors such as Confluent and MongoDB, Inc..

Features and Functionality

Payara implements the full Jakarta EE stack, including Servlet APIs, JavaServer Faces, Enterprise JavaBeans, Java Persistence API, and JAX-RS. It provides clustering, session persistence, and automated failover similar to features found in Apache Tomcat clustering and JBoss EAP domain management. Observability features align with standards adopted by Prometheus and OpenTelemetry, exposing metrics and health checks for consumption by Grafana dashboards and Kubernetes probes. Security integrations support OAuth 2.0 and OpenID Connect patterns comparable to implementations in Keycloak and Okta, and include role-based access control suitable for enterprise compliance regimes referenced by organizations like PCI Security Standards Council and ISO bodies.

Deployment and Administration

Deployment workflows support traditional virtualization platforms from VMware and public cloud providers such as Amazon Web Services, Google Cloud Platform, and Microsoft Azure. Containerized deployment is supported with images compatible with Docker (software) and orchestration on Kubernetes (software), aligning with patterns from Helm (software) charts and Istio service mesh integrations. Administration is facilitated through a web-based admin console, CLI, and RESTful management endpoints resembling interfaces offered by Tomcat and WildFly. Backup, upgrade, and rolling deployment strategies follow practices advocated by CNCF projects and enterprise DevOps tooling like Jenkins and GitLab.

Performance and Scalability

Payara emphasizes runtime optimizations and scalability features to support high-throughput transactional systems used by fintech and ecommerce firms such as Stripe (company) and Shopify. Through JVM tuning, connection pool management, and clustering, Payara can scale horizontally across nodes orchestrated by Kubernetes (software), leveraging autoscaling policies similar to those in Amazon EC2 Auto Scaling. Benchmarks and tuning guides often reference garbage collectors and performance practices documented by Oracle Corporation for the HotSpot (virtual machine), and comparative analyses with Apache Tomcat and Jetty (web server) highlight trade-offs in throughput, latency, and memory footprint.

Community and Ecosystem

The Payara ecosystem includes contributors, commercial maintainers, and partners in consulting and cloud hosting reminiscent of communities around GlassFish, Apache Tomcat, and WildFly. Community resources include mailing lists, issue trackers, and forums paralleling governance models used by Eclipse Foundation and Apache Software Foundation projects. Third-party integrations and extensions are provided by vendors in the Red Hat and IBM ecosystems, as well as independent tooling from companies like HashiCorp and Datadog. Training, certification, and events involving speakers from Devoxx and JavaOne augment adoption and knowledge sharing across enterprises and developer communities.

Category:Application servers