When commercial support for GlassFish ended in 2014, Payara Server was created from the open source code as a fully supported drop-in replacement for GlassFish.  

Payara Services was born in 2016 to offer support solutions for Payara Server. By 2017, Payara Services had joined The Eclipse Foundation and the Payara Platform expanded to include Payara Micro and comprehensive commercial support options for development projects, in-production support, and consultancy solutions.  New product features and the development of the Payara Platform evolves and is improved upon with each monthly release, and while the application server was originally derived from GlassFish and shares many similarities - the two products are not the same. 

Last week, we announced our exciting new webinar series, 'Dismiss the Myths: Get to Know Jakarta EE (Java EE). This is a series of 6 webinars, every Wednesday at 3.00pm BST for the next 6 weeks - with the first one taking place this Wednesday! 

Our CEO and FounderSteve Millidge is leading this series, taking one common misconception about Jakarta EE ( previously Java EE ) at a time. Turns out, you might be wrong in thinking Java is behind the times...

This is also the perfect webinar series if you have heard Jakarta EE or Java EE mentioned but aren't sure what it is, what the namespace change means or where its future lies. Steve will be catering to users who are new to the technology as well as long-time Jakarta EE developers. 

When using Kubernetes, for more complex scenarios it is not enough to start the deployment or service. You also need to execute some commands within the containers to perform some configuration or initialization of the environment.

To automate configuration or the process of initializing an environment, you can write a Kubernetes operator.The Payara Kubernetes Operator, released as a Proof of Concept or Minimum Viable Product (MVP) in our June Payara Platform release, helps you to set up a Payara cluster using the Deployment Group feature of the Payara Server.

These days, it seems Kubernetes is a topic that is never too far from people's lips.  The tool, and the associated tools built around it, are talked about so often it seems it's the only subject important to developers these days - especially as the IT world becomes increasingly orientated towards cloud and microservices.

But in spite of all the conversation around Kubernetes... do you really need Kubernetes for your environment? Or is it just another case of the next 'new and shiny' object,  with people distracted by the novelty and possibility, rather than the facts? In this blog, I'll take a closer look at why Kubernetes might be a case of the hype outweighing the helpfulness in most cases. 

Payara Platform is an open source middleware platform. This means that we are proud to nurture and grow an open and collaborative community, building on the needs of all to advance our software. 

Part of this ethos is inviting contributions to our software via our GitHub. Users can issue a pull request with suggested bug fixes and enhancements, and if successful, these will incorporated in our next release. We send t-shirts and stickers to contributors to say thank you! 

Since our last contributor shout out in February, we've implemented many useful pull requests, from valued long time contributors Alexander Pinchuk and Oliver Bertuch, as well as new contributorAngelTG2.

We also wanted to take the opportunity to point out that contributions aren't the only way to shape the future of Payara Platform. You can also up or down vote the open issues - new features, enhancements and bug fixes - that would make the most positive difference to YOUR development and applications. Find out more below. 

Running your application sometimes requires multiple instances to handle the requests of the users. Within the Payara Platform, the Domain Data Grid helps you configure your environment to run your application in a cluster. Besides the setup of a cluster itself, many applications can benefit from an environment that scales dynamically.

The number of instances must increase when the application usage peaks and should decrease when activity is low to reduce the resource usage and the corresponding costs associated with it. The introduction of the AutoScale feature in Payara Server Community 5.2021.4  helps us achieve this dynamic scalability.

The June 2021 Payara Platform release is here!  Payara Enterprise 5.28.1 includes 5 bug fixes and 2 component upgrades along with a community contribution from AngelTG2 for improving loading time for REST applications when there are many password aliases.

In addition to the bug fixes, component upgrades, and community contribution improvement, the Payara Community 5.2021.4  release also introduces a new AutoScale feature in Payara Server to achieve dynamic scalability of instances based on application usage.

You can download Payara Platform Community 5.2021.4 here and request Payara Platform Enterprise 5.28.1here. 

Read more below to find out the details.

The big community news of this month was the release of Jakarta EE 9.1! The Eclipse Foundation brought out Jakarta EE 9.1 Platform and Web Profile specifications and related TCKs - the first release since the breaking namespace change to jakarta. We've rounded up our articles & announcements on this subject below - and watch this space, as Payara Platform is very close to launching our own Compatible Implementation. 

We also released the results of our Payara Platform Survery 2021 . Read in fullhere, including what we've learnt about the infrastructure you are using with the Payara Platform, what features you want to see, and our findings on how our users are adopting MicroProfileAPIs and new Jakarta EE versions. 

We're already using the results of the survey to shape content that responds to recurring issues users are encountering. See Rudy'sblog on why you might be finding Payara Server slow and an easy fix you may not have tried, as issues with deployment speed was a common theme in our survey results. 

As well as Payara's own content, the 'Monthly Catch' also includes our pick of the best from Java EE/Jakarta EE, MicroProfile, Java SE and DevOps influencers and authors this month, and wider industry news. We hope you enjoy, and make sure you are following us onLinkedIn and Twitter, and signed up to our blog, to get this content as it comes! 

Earlier this week, Jakarta EE 9.1 was released. This is an update to Jakarta EE 9, adding support for JDK 11 - you can read more about it in our bloghere.

Alongside the Jakarta EE 9.1 release, GlassFish 6.1 has been released as a Compatible Implementation. 

However, although GlassFish is still used by many - a legacy of the time it was supported by Oracle - we would argue it is NOT a good choice for running your enterprise applications in production.

If you are considering updating to more recent GlassFish versions, it might be better to consider more reliable, supported, and up-to-date alternatives. In this blog, I explain why GlassFish 6.x is not the best choice for your mission critical deployments.

Payara Services are celebrating the release of Jakarta EE 9.1 Platform and Web Profile specifications and related TCKs.

With Jakarta EE 9.1, global source community Eclipse Foundation brings to Java developers the first incremental Jakarta EE release since the new namespace was introduced last year. Read the Eclipse Foundation announcement here - featuring a quote from our Founder and CEO Steve Millidge.

Payara's team have not only worked hard to ensure Jakarta EE 9.1 applications can be run in Payara Platform 5, but Payara Platform 6 alpha one is very close to being ready as a Compatible Implementation. Watch this space!