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)

Index

As this ebook edition doesn't have fixed pagination, the page numbers below are hyperlinked for reference only, based on the printed edition of this book.

A

adapters 23

driven 56

driving 47

incoming 47

outgoing 56

persistence 55

web 49

anemic domain model

versus rich domain model 44

application context 94

application layer 29, 30

application service 23

architecture boundaries 107-109

architecture/code gap 29

Architecture Decision Records (ADRs) 101

ArchUnit 111

assembling 91, 92

via plain code 93, 94

via Spring’s classpath scanning 94-96

via Spring’s Java Config 96-98

authentication 49

authorization 49

B

beans 94

Behavior-Driven Development 72

big ball of mud 4, 116

big design up front (BDUF) 4

boundaries

enforcing 107

bounded context 60, 119-121

appropriately coupled 123-125

decoupled 122, 123

Broken Windows Theory 12, 99, 100

...