Foojay community members discuss the modernization of Jakarta EE applications from the older Java EE form, including backwards-compatibility, as well as forwards-excitement about cool new developments like Microprofile.
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 article, I’ll take a closer look at why Kubernetes might be a case of the hype outweighing the helpfulness in most cases.Rudy De Busscher
When AutoScale is fully developed, not only will it allow you to change the number of instances in the Deployment Group by implementing additional asadmin commands, but it will also signal the routing systems of the changed configuration and automatically trigger a change in size based on rules around resource usage.
In this first step of the AutoScale development, we have introduced the concept of the Scaling Group into Payara Server Community Edition 5.2021.4 which can alter the number of instances in a Deployment group and implement it for SSH nodes.
The AutoScale feature is in continuous development, with improvements and additional functionality (including addressing the routing issue) planned in our future releases.
In this article of the Getting Started with Jakarta EE series, we look at various specifications and how you can use them in your next application.
We explain a few features of Context and Dependency Injection (CDI). The CDI specification is an important backbone of Jakarta EE as it brings several specifications together. Over the years, it became more and more important as an increasing number of specifications started using CDI as the basis for it.
In this article, we will also tell you a bit about the different scopes, the interceptor mechanism, and the Event system.
In this second article of the Getting Started with Jakarta EE 9 series, we show you some basic scenarios using the REST specification.
Although most people are using the term REST or RESTful API just to indicate they do data transfer over HTTP, and ignore the “Hypermedia as the engine of application State (HATEOS)” part of REST. The technology is used a lot lately to connect the front-end with the back-end.
For those who are not familiar with Jakarta EE, this article should give you an indication how to create such a REST API with Jakarta EE 9.
We decided to start a ‘Getting Started with Jakarta EE 9’ a blog and video series to introduce those who are not familiar with the platform to the basics of Jakarta EE 9.
The release of Jakarta EE 9 breaks a tradition of Java Enterprise. A legal requirement of the Java EE code donation from Oracle to the Eclipse Foundation is the change of the namespace of javax to jakarta.
But the change of the package and XML namespace in Jakarta EE 9 is only the beginning. The change of the namespace allows for new development and functionality, but all frameworks and libraries using one of the Java Enterprise specifications also need to be adjusted to the new version.