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)

Start simple

An important point that took me far too long to realize is that software architecture isn’t just something we define at the beginning of a software project that will take care of itself after. We can’t know everything we need to know to design a great architecture at the beginning of a project! The architecture of a software project can and should evolve over time to adapt to changing requirements.

This means that we won’t know which architecture style will be the best for the software project in the long run, and we might need to change the architecture style in the future! To make this possible, we need to make certain that our software is supple to change. We need to plant a seed of maintainability.

Maintainability means that we need to make our code modular so that we can work on each module in isolation and move it around in the code base, should the need arise. Our architecture needs to make the boundaries between those modules as clear...