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

Navigating the Java mapping landscape – evaluating framework trade-offs

You can now understand the motivations for using layers. It’s great that we have a mature Java ecosystem and don’t have to do everything manually – thanks to the frameworks. Since there are so many of them, we can categorize them based on API usability, proximity, and runtime.

  • Usability: One of the items to evaluate when looking at a framework is the usability of its API. For instance, you can ask a question such as “How many times can we use the same API with different databases? Is it even possible?
    • Agnostic API: A single API can be used with multiple database vendors, types, or paradigms. The positive aspect of this is that an agnostic API reduces the cognitive load since you don’t need to learn about a new API for every different database integration. However, you might lose particular database behaviors or have to wait longer to receive feature updates...