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)

Trust your experience

We’re creatures of habit. Habits automate decisions for us, so we don’t have to spend time on them. If there’s a lion running toward us, we run. If we build a new web application, we use the layered architecture style. We have done it so often in the past that it has become a habit.

I’m not saying that habitual decisions are necessarily bad decisions. Habits are just as good at helping to make a good decision as they are at helping to make a bad one. I’m saying that we’re doing what we’re experienced in. We’re comfortable with what we’ve done in the past, so why should we change anything?

Therefore, the only way to make an educated decision about an architecture style is by having experience in different architecture styles. If you’re unsure about the Hexagonal Architecture style, try it out on a small module of the application that you’re currently building. Get used to the concepts...