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)

Evolve the domain

Over time, we learn more and more about the requirements of our software, and we can make better and better decisions about the best architecture style. The application might evolve from a collection of simple CRUD use cases to a rich domain-centric application with a lot of business rules. At this point, the Hexagonal Architecture style becomes a good option.

It should have become clear in the previous chapters that the main feature of a Hexagonal Architecture style is that we can develop domain code free from diversions, such as persistence concerns and dependencies on external systems. In my opinion, evolving domain code free from external influence is the single most important argument for the Hexagonal Architecture style.

This is why this architecture style is such a good match for DDD practices. To state the obvious, in DDD, the domain drives the development, and we can best reason about the domain if we don’t have to think about persistence concerns...