Posts tagged Payara Platform 5
The 2021 Payara Platform Survey was completed in April. Our surveys help us shape the future of Payara Server and Payara Micro as they give us an idea what features and enhancements the community would like to see in future releases. Surveys also provide an opportunity for you to tell us what needs to improve and after finding 14% of respondents indicated the speed of deployment is not as fast as they would like, we wanted to share a tip.
When a user needs to access multiple applications in your environment, you should not require authentication for each application. If the user has already been authenticated for one of the applications, he or she should should not be asked for credentials when he accesses one of the other applications during the same browser session. This concept is called Single Sign-on where the authentication credentials are 'shared' in the environment and can be used by any application in that environment.
The Domain Data Grid feature of the Payara products is powered by the Hazelcast library. It provides the necessary functionality for the Deployment Group (clustering functionality), Cache functionality, CDI cluster singleton, and monitoring data storage within Payara to name just a few features.
Since Hazelcast can cluster multiple instances into a data grid, it is possible to create a Hazelcast grid that comprises the Payara instances and some other instances included in other applications running outside of Payara.
The release of Jakarta EE 9, at the end of 2020, was in many ways a historic event. The Java Enterprise framework is already 20 years old, having its first release in 1999. It has changed names a few times but the main concepts of the first release can still be found in this new release. During all those years, it has adapted itself to keep it up to date but has always adhered to its main principle of stability and backward compatibility.
The Payara Platform 2021 Survey is underway and we're inviting everyone to answer a few questions about your use of the Payara Platform and ecosystem components. We want to know what you like, what you want to see improved, and we're giving you the opportunity to vote on new features you'd like to see added to the Payara Platform.
The Payara Platform 5.2020.3 release (coming soon!) introduces major refactoring and architectural changes to the underlying implementation of MicroProfile OpenAPI 1.1.2.
The goal of the OpenAPI specification is to provide a standard format for documenting REST API services which is extremely useful, as it follows a standard and it can be used in a range of tools such as those provided by the Swagger suite. These let you do all sorts of things such as design, edit, and test a REST API documented by an OpenAPI document.
The runtime image of Payara Server consists of over 400 modules. Half of these do not come directly from the Payara codebase, but are various third-party APIs, their implementations and helper libraries. How do you choose the correct versions of your application's libraries so they are not in conflict with the ones in the server runtime?
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.