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...