Hexagonal architecture is a pattern of design that aims for a separation of concerns. It produces a decoupled system, where business rules are independent of the framework, UI or the database used.
There are two big benefits of using it. First, it is possible to test our business rules without the need of any UI, database or webserver. Second, it is possible to change any concrete implementation without affecting the core of our application, making framework updates easy.
In this talk, we will see the ongoing application of hexagonal architecture to Entrápolis, our ticketing product. Thought its code is not old, a dozen of developers have worked on it, mostly without any proper guidance, resulting in a code hard to maintain, hard to optimize and hard to add new features.
We will not only see the benefits of applying hexagonal architecture to our monolith, but also the missteps and drawbacks we encountered.
I just submitted again to helpmeabstract.com in case that someone is willing to take a look at the new, improved version. If not, that would be okay, I already had great help :)