Jakarta EE is the most popular Java server-side framework, way ahead its alleged competitors such as Spring, Quarkus, Micronaut or Dropwizard. With the industry-wide adoption of microservices based architectures, its popularity is skyrocketing and, during these last years, it has become the preferred framework for professional software enterprise applications and services development in Java.
In this blog, I'll explain more about Jakarta EE from my perspective as a Senior Java software architect/developer and why Jakarta EE and its runtimes beat the competition, in my opinion!
These days the world-wide open-source community celebrates the advent of Jakarta EE 10. It is then a good time to look at one of its most relevant and, at the same time, unknown parts: security!
In this blog, I'll give an introduction to Jakarta EE Security, and then explain how Payara Platform builds on Jakarta EE Security with built-in identity stores for RDBMS (Relational Database Management System) and LDAP (Lightweight Directory Access Protocol).
Payara Engineering have recently released Payara Server Community 6 Alpha 3 and Payara Server Community 6 Alpha 4 as major milestones on the road to full Jakarta EE 10 support.
In this blog, we will explore what these releases can do and how you can use them to help in your migration to Payara 6 and Jakarta EE 10.
Payara 6 Community Alpha 4, out today, is suitable for trying out Jakarta EE 10, and marks a key step on the road to full Jakarta EE 10 compatibility for Payara Community.
Also out this month is Payara Enterprise Version 5.43.0, and a release of Payara Platform Version 4.x in its extended support phase.
Jakarta EE 10 will be released on September 22! It's almost here...
While the previous releases of Jakarta EE have been focussed on the much-feared namespace change and updating everything with support for Java 11, this is the first major release of Jakarta EE to start introducing new features for developers to use. I’ll cover some of them here.
Payara Cloud provides an easy-to-use user interface to allow your application to run in a managed cloud environment. While this is very convenient for configuration and troubleshooting work, integration in continuous deployment pipelines calls for something else.
Our answer is deploying to Payara Cloud using a GitHub Action Workflow and Payara Cloud Command Line (PCL).
August is typically a quiet month, and whilst this is the case in terms of industry announcements, there have been incredible learning resources and general Java articles created. Here, we have rounded up some of the best of them, covering DevOps, cloud computing, Java, Jakarta EE, MicroProfile and open source.