Posted on

NoSQL, the Cloud, and Java: Part 2: The NoSQL Platforms

Within the world of NoSQL solutions with Java, there are several solutions and different types, which was the first part of this article. However, in addition to the keys, there are also platforms. The platforms are a set of tools that help to work with NoSQL databases. In this post, you will have the objective of talking about the platforms: the definition and the existing solutions in the current environment with Java.

An important point to start the discussion about NoSQL platforms is that, like NoSQL description themselves, there is no single definition. It can differ according to the literature and experience of each author. In a general way, NoSQL solution platforms are a set of tools to deal with databases. That is, in addition to the API, there will be other tools.

Posted on

Jakarta Security and Rest in the Cloud: Part 2 Getting to Know the Basics

Security is generally a topic that we always leave out when we talk about software architecture, but that does not mean that it is not essential. To talk more about the subject, we created this series on Java API security with Jakarta EE. In this second part, we will speak of the BASIC authentication process, how to implement it with a non-relational database, in this case, MongoDB, and how to quickly take it to the cloud.

BASIC is an authentication process where the user needs to enter their respective credentials, such as username and password, through each request in the header when they want to make a request to the server. In this case, the request header will have an Authorization: Basic <credential> where the credential is the username and password separated by “:” encoded using Base 64.

Posted on

Get to Know JSF: An Easy and Straightforward a Jakarta Framework

Developing web systems is a reality in the current market, and the Jakarta Server Faces framework is a standard Jakarta EE option to solve this type of problem. One of the characteristics of JSF is to work in a way oriented towards screen components and their events (for example, clicks). In this way, we can associate these components with different aspects of our system, such as the execution of business operations, value conversions, field validations, etc. In this article, we'll talk about this JSF and how to move this application to the cloud with Platform.sh.

To celebrate the new year, let's create a small wish list in Java with Jakarta EE technologies. In the front end, we'll use Java Server Faces (JSF), a Java-based web application framework that simplifies the development and integration of web-based user interfaces with several already-made components. To store the list, let's use MongoDB.

Posted on

What’s New With Jakarta NoSQL? (Part II)

Moving to Cloud-Native

Cloud computing has brought many methodologies and techniques that have revolutionized both the business and technical worlds. Among the terms that came up were cloud-native. To meet and cover these expectations in the Java universe, Jakarta EE emerged. The purpose of this post is to talk about the concept of cloud-native and to run an application with this concept using the latest milestone version of Jakarta EE NoSQL.

You may also like: From javax.* to jakarta.*: A Simple Proof of Concept

Posted on

What’s New With Jakarta NoSQL? (Part 1): Intro to Document With MongoDB

Jakarta EE picks up where Java EE 8 left off, but the roadmap going forward will be focused on modern innovations like microservices, modularity, and NoSQL databases. This post will talk about the newest milestone version of this new specification and the subsequent actions to make the Jakarta EE community even greater in the cloud.

Why Jakarta NoSQL?

Vendor lock-in is one of the things any Java developer needs to consider when choosing NoSQL databases. If there’s a need for a switch, other considerations include time spent on the change, the learning curve of a new API to use with this database, the code that will be lost, the persistence layer that needs to be replaced. Jakarta NoSQL avoids most of these issues through Communication APIs. Jakarta NoSQL also has template classes that apply the design pattern ‘template method’ to database operations. And the Repository interface allows Java developers to create and extend interfaces, with implementation automatically provided by Jakarta NoSQL — support method queries built by developers will automatically be implemented for them.

Posted on

Microservices in the Cloud, Part Two

Are there microservices in these clouds?

Microservices are a hot topic in software design, and for good reason. They have plenty of advantages when it comes to handling infrastructure complexity, many of which were addressed in part one of our related Java posts. Now, it’s time to talk about the code and design. In this post, we’ll take a deep dive into each module.

You may also like: Microservices in the Cloud, Part One

When creating an application, clean code means thinking about design and architecture. Architecture is the software process that handles flexibility, scalability, usability, security, and other points, so you have more time to focus on business rather than on technology. Some architecture examples include: