Book Image

Get Your Hands Dirty on Clean Architecture

By : Tom Hombergs
Book Image

Get Your Hands Dirty on Clean Architecture

By: Tom Hombergs

Overview of this book

Building for maintainability is key to keeping development costs low and processes easy. 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. With this comprehensive guide, you’ll explore the drawbacks of conventional layered architecture and the advantages of domain-centric styles such as Robert C. Martin's Clean Architecture and Alistair Cockburn's Hexagonal Architecture. Then, you’ll dive into hands-on explanations on how to convert hexagonal architecture into actual code. You'll learn in detail about different mapping strategies between the layers of hexagonal architecture and discover how to assemble the architectural elements into an application. Additionally, you’ll understand how to enforce architecture boundaries, which 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.
Table of Contents (13 chapters)

The Responsibility of Starting Clean

While working with code doesn't really feel like looting a car, we all are unconsciously subject to Broken Windows psychology. This makes it important to start a project clean, with as few shortcuts and as little technical debt as possible. Because, as soon as a shortcut creeps in, it acts as a broken window and attracts more shortcuts.

Since software projects are often very expensive and long-running endeavors, keeping broken windows at bay is a huge responsibility for us as software developers. We may even not be the ones finishing the project and others have to take over. For them, it's a legacy codebase they don't have a connection to, lowering the threshold for creating broken windows even further.

There are times, however, when we decide that a shortcut is a pragmatic thing to do, be it because the part of the code we are working on is not that important to the project as a whole, or that we are prototyping, or for economical reasons...