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)

Hexagonal Architecture

The term Hexagonal Architecture stems from Alistair Cockburn and has been around for quite some time.4 It applies the same principles that Robert C. Martin later described in more general terms in Clean Architecture.

4 The primary source for the term "Hexagonal Architecture" seems to be an article on Alistair Cockburn's website at https://alistair.cockburn.us/hexagonal-architecture/.

Figure 3.4 – A Hexagonal Architecture is also called a “Ports and Adapters” architecture since the application core provides specific ports for each adapter to interact with

Figure 3.4 – A Hexagonal Architecture is also called a “Ports and Adapters” architecture since the application core provides specific ports for each adapter to interact with

Figure 3.4 shows what a Hexagonal Architecture might look like. The application core is represented as a hexagon, giving this architectural style its name. The hexagon shape has no meaning, however, so we might just as well draw an octagon and call it “Octagonal Architecture.” According to legend, the hexagon was simply...