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)

What about read-only use cases?

As of now, we have discussed how we might implement a use case that modifies the state of our model. How do we go about implementing read-only cases? Let’s assume the UI needs to display the balance of an account. Do we create a specific use case implementation for this?

It’s awkward to talk of use cases for read-only operations like this one. Sure, the UI needs the data for a use case we might call View Account Balance, but in some cases, calling this a “use case” is a bit artificial. If this is considered a use case in the context of the project, by all means, we should implement it just like the other ones.

From the viewpoint of the application core, however, this is a simple query for data. So, if it’s not considered a use case in the context of the project, we can implement it as a query to set it apart from the real use cases.

One way of doing this within our architecture style is to create a dedicated...