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

Understanding DDD and Jakarta

DDD is an approach to software development that focuses on understanding the problem domain and modeling it in code. DDD is based on the idea that the problem domain should be the primary focus of development and that the software should be designed to reflect the underlying domain concepts and processes.

DDD distinguishes between strategic and tactical design. Strategic design refers to the overall architecture and organization of the software, while tactical design refers to the detailed design of individual components and modules.

In strategic design, DDD emphasizes the importance of defining a clear and consistent domain model that represents the business concepts and processes in the problem domain. This model should be independent of any particular technology or implementation and should be based on a deep understanding of the domain. Strategic design also involves defining bounded contexts and specific domain areas with well-defined boundaries...