Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Get Your Hands Dirty on Clean Architecture

You're reading from   Get Your Hands Dirty on Clean Architecture Build ‘clean' applications with code examples in Java

Arrow left icon
Product type Paperback
Published in Sep 2019
Publisher Packt
ISBN-13 9781839211966
Length 156 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Tom Hombergs Tom Hombergs
Author Profile Icon Tom Hombergs
Tom Hombergs
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

About the Book 1. What's Wrong with Layers? 2. Inverting Dependencies FREE CHAPTER 3. Organizing Code 4. Implementing a Use Case 5. Implementing a Web Adapter 6. Implementing a Persistence Adapter 7. Testing Architecture Elements 8. Mapping Between Boundaries 9. Assembling the Application 10. Enforcing Architecture Boundaries 11. Taking Shortcuts Consciously 12. Deciding on an Architecture Style

Deciding on an Architecture Style

So far, this book has presented an opinionated approach to building a web application in a hexagonal architecture style. From organizing code to taking shortcuts, we have answered many questions that this architecture style confronts us with.

Some of the answers in this book can be applied to the conventional layered architecture style. Some answers can only be implemented in a domain-centric approach such as the one proposed in this book. And some answers you might not even agree with, because they don't work in your experience.

The final questions we want answers for, however, are these: when should we actually use the hexagonal architecture style? And when should we instead stick with the conventional layered style (or any other style, for that matter)?

The Domain is King

It should have become obvious in the previous chapters that the main feature of a hexagonal architecture style is that we can develop the domain code free from diversions...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime