I like Payara Server's easy installation and powerful administration interface (both CLI and web) facilitating server configuration and application deployment.
Vibrant and supportive community and, with Payara Server, one can get professional support if needed.

Antonio Rocha

My favourite Payara Server features include:

- Integrated support for JCache (JSR 107)
- Ability to work with CDI events across a cluster (inter-JVM)
- Automated clustering of Payara Micro instances
- Versatile: Java EE 7 full + web profile (in embedded form as well) along with a ‘micro’ mode !
- Quarterly releases with bug fixes, enhancements as well as upgraded versions of Java EE implementations (Jersey, Tyrus etc.)

I would love to use Payara Server (any flavour) in production, but that’s currently not the case. I love contributing to Payara Server because:

- The project is well managed via GitHub & the Payara folks are welcoming, easy to reach out to and work with. They even send you cool swag ! ;-)
- Issues/bugs/enhancements are actively tracked and worked upon
- Always looking to innovate and developing new & interesting features
- Simplicity - this makes it easy for the community to chime in and contribute

I would recommend Payara Server to anyone who is looking for a solid GlassFish replacement or even a full fledged, versatile and buzzword compliant Java EE runtime :-)

Abhishek Gupta
@abhi_tweeter | Blog


I use Payara Server both for education and for some in-house systems. I also use Payara Micro for various Java EE demonstrations. Payara Server fits any purposes and always meets my expectations. I can certainly recommend Payara Server for Java EE applications.

Kenji Hasunuma
@khasunuma | Coppermine

We've been using Payara Server and its predecessors for some 14 years now. We tried to upgrade to GlassFish 4, but it was not so simple because of some bugs in GlassFish. We tried to fix GlassFish's sources and send patches to GlassFish, but the response was too slow and weak. Finally, Reza Rahman helped us and recommended the Payara Team to me. Then things went fast - after several days our patches were reviewed and merged. Now we can simply cooperate with the Payara Team on fixes and future development. Since then, Payara Community has been growing and the application server gets better and better.

At this time we use these technologies implemented by Payara: JDBC, JPA, JTA, JAX-WS, JAX-RS, JSF, JSP, JCACHE, EJB, CDI and Java Concurrent API. We also use the Embedded Payara Server with the Arquillian for automatic integration tests. Our biggest EAR application contains around twenty war/ejb modules, and runs in a clustered Payara Server domain. Some parts were written in Java 1.4 (2002) and the application is still compatible with Java EE7 (8) with only minor changes, some parts are modernised and some are brand new. This is a real evolution - nobody can recreate same application in any team in one year, but we can still use new technologies and replace weak old parts little by little - all thanks to Payara!

David Matejcek
Twitter | Blog | GitHub | Stackoverflow 





← Back to Community


GlassFish v3 became the killer application server in 2009, then Oracle dropped the commercial support.

I was skeptical as Payara was announced at JavaOne 2014 conference in San Francisco and I was proved wrong. Since two years an endless stream of commit messages, pull requests and comments dominates my GitHub timeline.

The Payara Server is surrounded by vibrant community, nice engineers and capable support.

Particularly non-functional features important for devops, Continuous Deployment and “microservices” like convenient command line, extensive RESTful monitoring (used in LightFish), or nice admin web interface are important for enterprise projects.

Adam Bien
@AdamBien | Blog

Since Oracle dropped support for GlassFish, I've been looking for a replacement. I still think GlassFish architecture is the best on the market today, but due to lack of resources from Oracle, it became stale, and bugs weren’t fixed.

Then, I found Payara.  I was initially afraid that Payara Server wasn’t going to track GlassFish progress, but since that progress is so few and far between, this fear quickly dissipated.

I started using Payara Server and haven’t looked back. The killer feature has really been Hazelcast integration. This has finally enabled me to achieve zero-downtime deployment and upgrades.

Lenny Primak
@lprimak | Blog

GlassFish was always my favourite application server; Not just a reference implementation, but also very well thought out and competitive. I’ve invested significant time getting to know GlassFish and was sad to see commercial support fade away, along with features used by businesses. Never feeling quite at home with JBoss I was happy to see Payara come out last year. Payara Server has full commercial backing and is production ready while still retaining most of its original heritage.

Barry van Someren

Ever since we settled for Payara Server, we never looked back. My personal experience with the support is nothing short of exceptional, both from Payara as well as from the community: What would take 6-12 months to fix in GlassFish, gets resolved in Payara Server in days/weeks, and the more you contribute, the more you receive. As of today, Payara Server is stable, cutting edge, leaps ahead of GlassFish and as far as I know, it is the only open-source application server with the option of a paid support that does not require any changes in your code, dependencies or infrastructure.

Matyas Bene

Since Oracle dropped the commercial support for GlassFish, we were looking for an open-source application server solution and replacement that allowed us to leverage our existing Java EE platform, ease of deployment and transparency to our users. Payara Server allowed us to meet all of our goals and achieve significant cost savings in the process. With Payara Server's ease of installation and great support, what you get is open-source software that anyone thinking of successful deployment and implementation of Java EE in their environment needs to try!

Kai Uwe Pel
@kaiuwepel | WebNetProject