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)

It Depends

I would love to provide a list of multiple-choice questions to decide on an architecture style just like all those "Which Personality Type Are You?" and "What Kind of Dog Are You?" tests that regularly swirl around social media. I'm the "Defender" personality type and if I were a dog, I would apparently be a Pit bull.

But it isn't as easy as that. My answer to the question of which architecture style to choose remains the professional consultant's "It depends...". It depends on the type of software to be built. It depends on the role of the domain code. It depends on the experience of the team. And finally, it depends on being comfortable with a decision.

I hope, however, that this book has provided some sparks to help with the architecture question. If you have a story to tell about architecture decisions, with or without hexagonal architecture, I'd love to hear about it.

You can drop me an email at [email protected]...