The Big Ball of Mud is the most serious problem I see in the majority of the code bases I look at.
But why do we keep falling into that trap? What are the root problems behind it? How can we avoid, escape, and stay out of it?
In this talk, you will learn about the architecture mental map I use to answer these questions. We will briefly revisit a few established software development and architecture ideas and see how you can put them in your service to help keep the mud out of your application.
The main topics of the talk are:
The Big Ball of Mud problem
Overview of DDD, Hexagonal, Onion, Screaming, Clean, CQRS
How to organise the code base to reflect architecture boundaries
How to maintain the architecture boundaries