As the recent June release (download here!) marks the first official release since splitting our product into two separate software editions, Payara Platform Enterprise and Payara Platform Community, you may notice the versioning has been updated.

We're happy to announce that Payara Platform Community (5.2020.2) and Payara Platform Enterprise (5.20.0) Editions are out today! The Community Release includes 28 bug fixes, 13 improvements, 3 new features, and 5 component upgrades. You can download it here! 

Here's some detail of what's included in the 5.2020.2 Community release:

With the June Payara Platform releases, Payara Platform will support version 3.3 of the MicroProfile (MP) standard. This blog summarises what changed since 3.2 and how this affects the Payara Platform.

Starting with our June 2020 release (coming soon!), we’re rolling out separate editions of Payara Server and Payara Micro - collectively known as the Payara Platform.

Alot went down in May! notably Java's 25th anniversary and a whole swathe of articles, webinars and podcasts that went with it! It felt like there was a webinar everyday!

Below you will find a curated list of some of the most interesting news, articles and videos from the last month. Cant wait until the end of the month? then visit our twitter page where we post all these articles as we find them! 

For some time now there has been an undeniable growth of interest for Microservices. The core concept itself, however, is not that new.

Migrating from GlassFish to Payara Server can be a simple and straightforward process, made even simpler with the help of our 'GlassFish to Payara Server Migration Guide'.

Payara Micro is a lightweight middleware platform for containerized Jakarta EE application deployments, but it still provides a lot of APIs and functionality for developers. On top of all Jakarta EE Web Profile APIs, Payara Micro also supports a additional Jakarta EE APIs, and it also provides the same MicroProfile, Payara, and JCache APIs as our complete application platform, Payara Server. In this article, we’ll show you how to make use of Jakarta Messaging (JMS) in Payara Micro to send and receive messages to and from a JMS broker.

Migrating applications from WildFly to Payara Server can be a simple and straightforward process because both servers rely on the Jakarta EE (Java EE) specifications. However, there are differences in many areas because many Java EE APIs in WildFly and Payara Server are implemented by different components. Moreover, the configuration of certain aspects like external resources, high-availability and deployment is not covered by any specification and is, in fact, very different in both servers. Although Payara Server offers similar features as WildFly, they are often based on different technologies and concepts, and often also use different terminology. Therefore, before going into migration from WildFly to Payara Server, we’ll provide you with an overview of similar features and concepts that exist in both WildFly and Payara Server.