Book Image

Hands-On Software Architecture with Java

By : Giuseppe Bonocore
5 (1)
Book Image

Hands-On Software Architecture with Java

5 (1)
By: Giuseppe Bonocore

Overview of this book

Well-written software architecture is the core of an efficient and scalable enterprise application. Java, the most widespread technology in current enterprises, provides complete toolkits to support the implementation of a well-designed architecture. This book starts with the fundamentals of architecture and takes you through the basic components of application architecture. You'll cover the different types of software architectural patterns and application integration patterns and learn about their most widespread implementation in Java. You'll then explore cloud-native architectures and best practices for enhancing existing applications to better suit a cloud-enabled world. Later, the book highlights some cross-cutting concerns and the importance of monitoring and tracing for planning the evolution of the software, foreseeing predictable maintenance, and troubleshooting. The book concludes with an analysis of the current status of software architectures in Java programming and offers insights into transforming your architecture to reduce technical debt. By the end of this software architecture book, you'll have acquired some of the most valuable and in-demand software architect skills to progress in your career.
Table of Contents (20 chapters)
1
Section 1: Fundamentals of Software Architectures
7
Section 2: Software Architecture Patterns
14
Section 3: Architectural Context

Understanding Domain Driven Design

DDD takes its name from the book of the same name by Eric Evans (2003). The subtitle beautifully clarifies what the goal is—Tackling complexity in the heart of software.

In this section, we will learn about the domain model, ubiquitous language, layered architecture, DDD patterns, and bounded contexts.

DDD is a widely adopted modeling technique to build rich and expressive domains. It is considered to be behind modern approaches such as microservices development.

The idea behind DDD is discovering how to model our software in a way that mirrors the problem we are facing in the real world. It is expected that if properly modeled, our software will be readable, will adhere to requirements, and will work properly.

Of course, there is no magic recipe for that: DDD provides a toolkit of patterns, best practices, and ideas to implement this modeling. This approach works particularly well with complex domains, but it might be overkill...