Book Image

Persistence Best Practices for Java Applications

By : Otavio Santana, Karina Varela
Book Image

Persistence Best Practices for Java Applications

By: Otavio Santana, Karina Varela

Overview of this book

Having a solid software architecture breathes life into tech solutions. In the early stages of an application’s development, critical decisions need to be made, such as whether to go for microservices, a monolithic architecture, the event-driven approach, or containerization. In Java contexts, frameworks and runtimes also need to be defi ned. But one aspect is often overlooked – the persistence layer – which plays a vital role similar to that of data stores in modern cloud-native solutions. To optimize applications and data stores, a holistic understanding of best practices, technologies, and existing approaches is crucial. This book presents well-established patterns and standards that can be used in Java solutions, with valuable insights into the pros and cons of trending technologies and frameworks used in cloud-native microservices, alongside good Java coding practices. As you progress, you’ll confront the challenges of cloud adoption head-on, particularly those tied to the growing need for cost reduction through stack modernization. Within these pages, you’ll discover application modernization strategies and learn how enterprise data integration patterns and event-driven architectures enable smooth modernization processes with low-to-zero impact on the existing legacy stack.
Table of Contents (18 chapters)
1
Part 1: Persistence in Cloud Computing – Storing and Managing Data in Modern Software Architecture
6
Part 2: Jakarta EE, MicroProfile, Modern Persistence Technologies, and Their Trade-Offs
9
Chapter 7: The Missing Guide for jOOQ Adoption
11
Part 3: Architectural Perspective over Persistence

Exploring the Multiple Database Flavors

As a system evolves, especially within a microservices architecture, it becomes necessary to implement a polyglot persistence strategy to accommodate the individual needs of decoupled and independent services. This involves examining various options for storing data, including Database Management Systems (DBMSs) such as relational, NoSQL, and NewSQL databases. It is important to consider the application’s use case scenarios for each type of database in order to avoid overengineering the architectural design.

In this chapter, we will delve into the characteristics and advantages of both traditional relational databases and newer non-relational databases. We will also take a closer look at NewSQL databases and their place in the market.

Before delving into the application details, we’ll start by familiarizing ourselves with the multiple storage solutions that we can adopt as the persistence strategy of our solutions. The following...