Starting with the latest Payara Platform 201 release, we've made changes to how we build and report our future platform roadmap. We recently introduced the Payara Reef initiative to enhance our communication with the Payara community, and as part of the Reef initiative, we are also introducing the Open Roadmap for the Payara Platform.

We're proud to announce that our 2019 Community Survey results are now available! We conducted a survey between September and November 2019 to determine how organizations are using the Payara Platform and what ecosystem components are most commonly used with the platform. Thank you for contributing and helping us gain insight into which features and enhancements the community would most like to see in future releases of the Payara Platform.

Payara Micro instances can join a cluster automatically. They could also join the Domain Data Grid as well as standalone Payara Server instances. In this blog, I explain how to join Payara Micro instances to the Data Grid in the Admin Console.

With the summer season coming to a close, the time has come for a new release of the Payara Platform! Here's a quick list of the new features you'll have to look forward to with the Payara Platform 5.193 release:

The term “Kubernetes” comes from the Greek “kubernan,” which means to steer or guide. You can think of Kubernetes like a pilot for apps that are stored and run together in containers and other forms of workload distribution software. The Greek “kubernan” was transformed over the years to relate to the term “Govern”, which is another helpful comparison when trying to understand the full capacity of Kubernetes.

On the surface, the changes between Fault Tolerance 1.1 and 2.0 are straightforward. The main new feature is allowing use of the @Asynchronous annotation on methods returning CompletionStage which allows for more elegant composition of asynchronous computation.

An increasing number of organisations have moved, or are planning to move, to cloud-based hosting and are developing their applications to run in the cloud. However, once it's decided that your next application is going to run in the cloud, there are still a lot of architectural choices ahead of you. Besides obvious benefits like cost reduction, scalability and easier administration, cloud environments bring their own disadvantages and potential risks. In this blog, I'll share with you some tips on how to take care of the most important disadvantages and risks when you decide to build your applications for the cloud.

We will look at the various options for running your application:

Whilst cost is an important consideration when choosing a cloud provider, there are other things that you need to take into consideration before making your decision. To help, here are the top 5 tips for choosing the right cloud provider for projects based on Payara Server or Payara Micro and your business needs.

Several Cloud Providers have the possibility to run your Payara Platform Docker Images on their infrastructure. In this blog, I will describe to you how you can run your application on Microsoft Azure using a Docker Container. All the steps required to perform this are described using the Azure Portal (web-based application) and the Azure Command line.

HK2 is a rather old dependency injection (DI) framework and is used as the core of Payara Server. Created in 2007 by Kohsuke Kawaguchi (who is also the creator of the Hudson project, now Jenkins) at Sun Microsystems, it followed JSR 330 closely, which was the JSR that introduced the @Inject, @Named and @Qualifier annotations, the very annotations which are also heavily used in CDI.