Rudy De Busscher on foojay.io - Friends of OpenJDK

MicroProfile Config for Java SE

Thu, 13 Oct 2022 16:10:31 +0000

The MicroProfile Config specification is one of those attempts to create a specification around application configuration for the Java Enterprise world. In the past, there were already some other attempts within Java EE to define this specification for Java EE, but they were never finalised.

Currently, another attempt is in progress with Jakarta EE Config but since MicroProfile is closely related to Jakarta EE, it is the best available solution today. That is the reason why almost all Jakarta EE runtimes also support MicroProfile Config and the other specifications of the MicroProfile umbrella.

MicroStream - Part 5: Caching, Integrations and Clustering

Wed, 06 Jul 2022 07:11:38 +0000

In this last article of the series, we cover a few other MicroStream features: caching, clustering, and the integrations into other frameworks.

We have now covered three main aspects of MicroStream:

We have seen how you can configure the StorageManager to define where data is stored.
We have discussed the strategy that you should follow to make sure the changes are also reflected in the storage so that we do not lose data.
We described the serialisation framework of MicroStream that stores the objects in a binary format so that it survives a process restart.

In this last article of the series, we cover a few other features of MicroStream: caching, integrations into other products, and we discuss a major upcoming feature.

MicroStream Next-Generation Serialisation Engine

Wed, 29 Jun 2022 08:07:20 +0000

In this fourth part we go deeper into the Serialisation engine that is within MicroStream to store the Object graph in a binary format.

In the previous articles (part 1 , part 2 and part 3 ), we have already mentioned that MicroStream stores Java instances in storage in a binary way with a new, from the ground up created, serialisation framework.

In this article, we go a bit more in detail about the next generation Java serialisation that we have built to achieve the MicroStream Java Object database and how you can use it outside the functionality of storing the root object that makes up your database.

MicroStream: How to store your data?

Wed, 22 Jun 2022 11:10:55 +0000

In the third article of the MicroStream series, we go into the details what you need to do so that data is stored externally to survive the process restart.

In the previous articles in this series, we introduced the main features of the framework and how you can configure the StorageManager .

Java instances in memory are your database but the StorageManager makes sure that the data are persisted so that they are read the next time the runtime is started again.

MicroStream: Configure the StorageManager

Wed, 15 Jun 2022 08:04:11 +0000

In this second article in the series, we cover how to get started configuring the StorageManager of MicroStream!

As we have discussed in the introduction article of this series, MicroStream provides you with a solution to use Java instances in memory as your database.

You can access the data through getters, the Stream API, or any other method provided on the Java Objects.

This means ultrafast, no mapping required, and no external system for your data.

MicroStream: High-Performance Java-Native-Persistence framework

Mon, 06 Jun 2022 08:03:02 +0000

Within every application, data plays a very important role.

In every industry, you have data, such as customer or product information, analysis results, patient data, or account data is a vital part of the business and the applications that support your business processes.

Data must be in memory to be processed by your application, but must be stored outside of it because the application’s memory is temporary.

Information is lost when the process ends unless we have stored it somewhere else in a sustainable way.

Getting Started with Jakarta EE 9: Jakarta EE 9.1

Wed, 13 Oct 2021 08:02:33 +0000

Jakarta EE 9.1 was officially released at the end of May 2021.

The objective of Jakarta EE 9.1 is to provide certification on Java SE 11 and not to deliver new features. These are scheduled for Jakarta EE 10.

In this article, we describe how you can use Jakarta EE 9.1 and some background around Jakarta EE 9.1.

Using Jakarta EE 9.1

Just as with Jakarta EE 9, you can easily define all dependencies on Jakarta EE 9.1 for your web application by defining the jakarta.jakartaee-web-api artifact in your Maven pom file.

Foojay Podcast #3: Journey to Jakarta EE

Tue, 31 Aug 2021 14:26:29 +0000

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.

Podcast Apps

You can listen and subscribe to the Foojay Podcast on:

Spotify
Apple Podcasts
And most others…

Guests

Rudy De Busscher, product manager of Payara and EE contributor.
Josh Juneau, consultant and author of Jakarta EE Recipes .
Ivar Grimstad, Jakarta EE Advocate for the Eclipse Foundation .
Erik Costlow, Developer Relations for Contrast Security to secure Java/Jakarta EE applications.

Ask Yourself: Do You Really Need Kubernetes?

Wed, 07 Jul 2021 07:37:55 +0000

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 article, I’ll take a closer look at why Kubernetes might be a case of the hype outweighing the helpfulness in most cases.

Introduction to New AutoScale Feature Available in Payara Server

Wed, 23 Jun 2021 07:47:09 +0000

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.

Getting Started with Jakarta EE 9: Context & Dependency Injection

Wed, 26 May 2021 06:56:27 +0000

In the next part of the “Getting Started with Jakarta EE ” series, we discuss Context and Dependency Injection (CDI) and the CDI specification.

The CDI specification is an important backbone of Jakarta EE as it brings several specifications together. Over the years, it has become more and more important as an increasing number of specifications started using CDI as the basis for it.

We will also tell you a bit about the different scopes, the interceptor mechanism, and the Event system.

How to Create a REST API with Jakarta EE 9

Mon, 26 Apr 2021 07:18:39 +0000

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.

Getting Started with Jakarta EE 9: Hello World

Wed, 07 Apr 2021 08:55:22 +0000

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.

How to Convert a 3rd Party Library to the New Jakarta Namespace

Mon, 08 Mar 2021 16:56:53 +0000

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 tojakarta.

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.