Traditionally, enterprises stored their SQL data in relational database management systems (RDBMS). However, the strict and rigid SQL data format is not always fit for purpose...

This has led to the rise of schemaless databases and NoSQL. The distributed, non-relational model of NoSQL database technology made it the almost perfect choice for companies like Twitter, Google and Facebook that had amassed massive datasets from their web applications. 

But is it right for your enterprise? And will it work with Jakarta EE?

Jakarta EE 10 shipped with the fourth major release of its component based web framework Jakarta Faces. Hitherto known as Jakarta Server Faces, and Java Server Faces before that, Jakarta Faces, or just Faces,version 4.0is the first major version with API change since version 2.3 in Java EE 8. Among the major changes in this version are:

This post is inspired by Gunnar Morling'sposton a similar theme for the Java SE Platform. It is an opinionated guide to getting started developing applications on the Jakarta EE Platform. As an opinionated post, there may be some recommendations that you disagree with. That is natural. The post is directed at people just getting started and feel overwhelmed by all the options out there for getting started with enterprise Java. The post is broken down into the following sections;

It's January, and the Payara engineering bakery has been busy with the first release of the year. The Payara Platform Community 6.2023.1 release is hot out of the oven with 8 component upgrades, 1 improvement and 1 security fix. Payara Platform Enterprise 5.47.0 also comes with 14 component upgrades, 2 improvements, 3 bug fixes and 1 security fix. 

Jakarta EE has action and component based frameworks for building web applications using the model view controller architecture pattern. The much older Jakarta Faces is a component based framework while the much newer Jakarta MVC is an action based one. This blog starts by defining the two types, then takes a look at Jakarta MVC, what it is and how to get started.

In September 2022, the Jakarta EE community achieved a huge milestone with Jakarta EE 10 being released (read more here). The key goals of the Jakarta EE 10 release are simplicity, modernization and ensuring it is lightweight. It's been a few months since this major release, so we thought it's a good time now to do a bit of a recap. We invite you to join our series of fast-paced, no slides webinars that will bring you up to speed with Jakarta EE 10!

Using Payara Platform? You might be interested in what tools, OpenJDK versions and Jakarta EE releases our global community choose! 

We regularly conduct surveys to learn what technologies are most commonly used with Payara Platform, so we can work on our integrations and plug-ins.

This survey was promoted in October/November 2022 via social media, emails, blogs and our Payara Forum.

Batch processing is an integral part of enterprise applications. Reading, processing and storing vast amounts of data is mostly suited to batch processing runtimes that are optimized for such workloads. Inventory processing, payroll, report generation, invoice/statement generation, data migration, data conversion among others are all tasks that are suitable to batch processing.

Batch processing typically involves breaking data loads to be processed into smaller "chunks," which are also broken down into even smaller units for processing. The batch processing is then carried out on a single unit of the data, one at a time, without any human intervention. This makes the processing of a significantly large amount of data very efficient and fast. Batch processing can also be parallelized to take advantage of the hardware capabilities of the underlying computer. 

This blog series will show you how to create batch processing tasks on the Jakarta EE Platform. The blog is broken down into a series of posts, each blog covering a specific part of the batch specification. This blog introduces you to the Jakarta Batch specification and gives a high level overview of what constitutes a batch task.

The Jakarta Contexts and Dependency Injection API is the standard dependency injection framework on the Jakarta EE Platform. The latest version of the CDI specification that shipped withJakarta EE 10 is CDI 4.0. This release features a split of the core CDI API into Lite and Full. CDI Lite is designed to run in more restricted environments, and features a subset of the original features. CDI Full contains the Lite and all other features that were in core CDI in previous Jakarta EE releases.

Therelease of Jakarta EE 10marked the dawn of a new era for the platform. This release is the first major, community driven release of the platform since it was transferred to the Eclipse Foundation. As a community driven project, the platform is open for everyone to contribute to. One of the advantages of using Jakarta EE for your projects is that you can directly have a say in the direction and future of the platform. With Jakarta EE 10 out of the way, the focus will soon shift to the next release, Jakarta EE 11.