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

JPA state of affairs

JPA is a crucial Jakarta EE specification and the most mature data specification for enterprise applications. It provides a standardized and robust approach to ORM in Java, enabling developers to interact seamlessly with relational databases.

When working with the integration between Java applications and relational databases, several aspects need to be taken into consideration, such as the following:

  • Configuration management: How the configurations are externalized in order to be easily yet securely changed based on the environment in which it is being deployed (dev, prod, and so on).
  • Connection handling: Improper handling of connections with the database may lead to extra processing time, as it is expensive. This need is related to the requirement of managing open, close, and track connections with the database in order to use resources effectively and avoid having too many open and idle connections or not enough connections available to the application...