Having commercial support from Payara, who own the codebase, really takes open-source to the next level. They validated our configuration, made recommendations for improvement, and gave us confidence we were getting the most out of the product and making the best decisions from the start.
Payara is the de-facto middleware at Rakuten Card. We’ve found it wonderful to use, even for new hires – with Payara leveraging developers’ existing skill sets so no retraining is required.
Payara Platform is super stable and patches to issues are delivered faster than we notice them! For me, as developer, it is important to have access to a Nexus server where I can automatically download the latest releases.
The software has been tremendously easy to work with. Our transition from WebLogic to Payara Enterprise is still in progress and things are progressing nicely. We have found Payara Server Enterprise to be a lot more user friendly and approachable than WebLogic.
Overall, the migration from GlassFish 3 over to Payara Platform 5 was a straightforward process. There was no need for major code rewrites. Payara’s engineering team was clearly knowledgeable when answering the support tickets.
| Azul Payara version | Spec | Namespace | Java SE | MicroProfile |
|---|---|---|---|---|
|
7 (latest) |
Jakarta EE 11 |
jakarta |
21, 25 |
7.1 |
|
6 |
Jakarta EE 10 |
jakarta |
11, 17, 21 |
7.1 |
|
5 |
Java EE 8 |
javax |
8, 11, 17, 21 |
4.1 |
|
4 |
Java EE 7 |
javax |
7, 8 |
1.2 |
The cloud-native deployment shape, containers, Kubernetes, and serverless, for your existing Jakarta EE application, with no major rewrite. A Web or Core Profile application runs on both Azul Payara Server and Azul Payara Micro from one codebase, each on its own subscription, patched monthly across every supported version, from the vendor that also supplies the Java runtime.
Tooling built for single-JAR, container-native delivery on Azul Payara Micro. The Payara Micro Maven and Gradle plugins and the Maven archetype wire Azul Payara Micro into your build and CI/CD. Azul Payara Starter scaffolds the project, the Micro Managed Arquillian container runs your integration tests, and connectors for Kafka, Amazon SQS, Azure Service Bus, and MQTT connect your services to the systems around them.
Azul Payara follows a multi-phase lifecycle per major release, with Full Support, Extended Support, and Lifetime Support, and security patches backported across every supported major version so you upgrade on your own schedule. Azul Payara 4, 5, 6, and 7 are supported concurrently.
Move faster with hands-on help from Azul engineers. Azul Payara Accelerator offers focused Quick Start engagements and bespoke consultancy for tuning, monitoring, migration, training, and cloud adoption. Migration & Project Support adds engineering assistance and a private support portal while you build, before you reach production.
Our Java experts are ready to answer your questions and show how Azul Payara Server can support your secure, stable, and high-performance Java applications.
A cloud-native Jakarta EE 11 runtime in a single executable JAR of roughly 100 MB, with two-to-five-second startup, for containers, Kubernetes, and serverless. No installer ceremony, and no major rewrite.
Azul Payara Micro adds support with guaranteed critical-incident response, longer-term support, and security patches backported across supported versions. Azul Payara Micro Community is the free edition.
Azul Payara Micro adds enterprise-grade support with guaranteed SLAs, longer-term support, and security patches backported across supported versions. Azul Payara Micro Community is the free edition.
Yes. It is built for containerized and cloud-native environments and runs on any Kubernetes distribution.
Azul delivers support with guaranteed critical-incident response. Choose Standard or Premium.
No. Azul Payara Micro runs on any compatible JDK. Azul Core is available from Azul as a separate product, so the runtime and the JVM can come from one vendor.
Azul Payara Micro runs standard Jakarta EE archives. A Spring application built as a WAR deploys directly; a Spring Boot executable (fat) JAR is a different artifact and would need repackaging first.
Yes. Official multi-architecture Docker images are available.
