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)

One hexagon per bounded context?

When working with Hexagonal Architecture and multiple bounded contexts, our reflex is to create a separate “hexagon” for each bounded context. The result would look something like Figure 13.1.

Figure 13.1 – If each bounded context is implemented as its own hexagon, we need an outgoing port, an adapter, and an incoming port for each line of communication between bounded contexts

Figure 13.1 – If each bounded context is implemented as its own hexagon, we need an outgoing port, an adapter, and an incoming port for each line of communication between bounded contexts

Each bounded context lives in its own hexagon, providing input ports to interact with it and using output ports to interact with the outside world.

Ideally, the bounded contexts don’t need to talk to each other at all, so we don’t have any dependencies between the two. In the real world, however, this is rarely the case. Let’s assume that the bounded context on the left needs to call some functionality of the bounded context on the right.

If we use the architecture elements that Hexagonal Architecture...