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)

Managing Multiple Bounded Contexts

Many applications consist of more than one domain, or, to stick with Domain-Driven Design language, more than one bounded context. The term “bounded context” tells us that there should be boundaries between the different domains. If we don’t have boundaries between different domains, there are no restrictions on dependencies between classes in these domains. Eventually, dependencies will grow between the domains, coupling them together. This coupling means that the domains can no longer evolve in isolation, but can only evolve together. We could just as well not have separated our code into different domains in the first place!

The whole reason to separate code into different domains is so that these domains can evolve in isolation. This is an application of the Single Responsibility Principle, discussed in Chapter 3, Inverting Dependencies. Only, this time, we’re not talking about the responsibilities of a single class...