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)

Appropriately coupled bounded contexts

If all coupling could be avoided, software architecture would be a lot easier. In real-world applications, a bounded context very likely needs the help of another bounded context to do its work.

An example is again our bounded context that is concerned with money transactions. For security reasons, we’ll want to log which user has issued a transaction. That means that our bounded context needs some information about the user, which lives in another bounded context. But our bounded context doesn’t need to be tightly coupled to the user management context.

Instead of having to know the whole user object in our “transaction management” bounded context, it might be enough to just know the user’s ID. While a user object in the “registration” context is a complex object with many attributes, a representation of a user in the transaction context may only be a wrapper around the user ID. In the Send...