Book Image

Get Your Hands Dirty on Clean Architecture - Second Edition

By : Tom Hombergs
4 (1)
Book Image

Get Your Hands Dirty on Clean Architecture - Second Edition

4 (1)
By: Tom Hombergs

Overview of this book

Building for maintainability is key to keep development costs low (and developers happy). The second edition of "Get Your Hands Dirty on Clean Architecture" is here to equip you with the essential skills and knowledge to build maintainable software. Building upon the success of the first edition, this comprehensive guide explores the drawbacks of conventional layered architecture and highlights the advantages of domain-centric styles such as Robert C. Martin's Clean Architecture and Alistair Cockburn's Hexagonal Architecture. Then, the book dives into hands-on chapters that show you how to manifest a Hexagonal Architecture in actual code. You'll learn in detail about different mapping strategies between the layers of a Hexagonal Architecture and see how to assemble the architecture elements into an application. The later chapters demonstrate how to enforce architecture boundaries, what shortcuts produce what types of technical debt, and how, sometimes, it is a good idea to willingly take on those debts. By the end of this second edition, you'll be armed with a deep understanding of the Hexagonal Architecture style and be ready to create maintainable web applications that save money and time. Whether you're a seasoned developer or a newcomer to the field, "Get Your Hands Dirty on Clean Architecture" will empower you to take your software architecture skills to new heights and build applications that stand the test of time.
Table of Contents (18 chapters)

Boundaries and dependencies

Before we talk about different ways of enforcing architecture boundaries, let’s discuss where the boundaries lie within our architecture and what enforcing a boundary actually means.

Figure 12.1 – Enforcing architecture boundaries means enforcing that dependencies point in the right direction (dashed arrows mark dependencies that are not allowed according to our architecture)

Figure 12.1 – Enforcing architecture boundaries means enforcing that dependencies point in the right direction (dashed arrows mark dependencies that are not allowed according to our architecture)

Figure 12.1 shows how the elements of our Hexagonal Architecture might be distributed across four layers, resembling the generic Clean Architecture approach introduced in Chapter 3, Inverting Dependencies.

The innermost layer contains domain entities and domain services. The application layer around it may access those entities and services to implement a use case, usually through an application service. Adapters access those services through incoming ports or are being accessed by those services through outgoing ports. Finally, the configuration...