The objective of Jakarta EE 9.1 is to provide certification on Java SE 11 and not to deliver new features.
In this myth-busting webinar, Steve Millidge, founder of Payara, will show you why standards like Java EE (i.e., now Jakarta EE) are beneficial.
If you’ve been thinking standards like Jakarta EE don’t matter, this video will show you how having standards gives you the opportunity to develop future proof applications, among other benefits.
In this myth-busting webinar, Steve Millidge, founder of Payara, will show you why the Java EE/Jakarta EE deployment model is not old fashioned or out of date.
If you think you have to switch to Spring for a modern deployment model, this video will show you how the Jakarta EE deployment model using thin WARs allows you to modernize your application development, today!
If you’ve been hearing that Java/Jakarta EE is not Cloud-native or it’s difficult to get your Java/Jakarta EE applications running in the Cloud, watch this webinar to see why that’s not true and how you can continue using your existing Java/Jakarta EE development skills to modernize your application development!
In this myth-busting webinar, Steve Millidge (founder of Payara), demonstrates that Java/Jakarta EE application servers are not resource-heavy or slow.
Watch live demonstrations of application servers that show it’s possible to have a small footprint and low resource usage in Jakarta EE runtimes.
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.
To understand the philosophical and historical perspective on the Gang of Four’s design patterns, I made a short, 10-minute video, which was also my PluralSight Author Audition.
I came up with my own examples to understand design patterns further. Try downloading the code and see if it helps you in comprehending the patterns in a better way.
Some brief code snippets follow each pattern so you can get quick demonstrations. Feel free to bookmark this article as a quick reference/cheat sheet for when you want to quickly review each of them.
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.
Welcome to the next part of a series of articles on key concepts in Core Java and J2EE. The series revolves around memory architecture, connection and memory leaks, core Java syntax and semantics, Java Object layout/anatomy, multi-threading, asynchronous task execution, design patterns, Java agents, class loading, API design, OOPs & SOLID.
Today, we learn about the evolution of the Java Memory Architecture, post Java 7.0.