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)

How does this help me build maintainable software?

Component-based architecture is very simple. As long as each component has a dedicated namespace, dedicated API and internal packages, and classes within an internal package are not called from the outside, we get a very maintainable code base consisting of many composable and re-composable components. If we add the rule that components may be composed of other components, we can build a whole application out of smaller and smaller parts where each part solves a simpler problem.

Even though there are loopholes to get around the rules of the component architecture, the architecture itself is so simple that it’s very easy to understand and communicate. If it’s easy to understand, it’s easy to maintain. If it’s easy to maintain, the loopholes are less likely to be exploited.

Hexagonal Architecture cares about boundaries at the application level. Component-based architecture cares about boundaries at the...