Big ball of mud
A system with no visible structure: everything depends on everything, so every change is risky and nobody can explain where a rule lives.
Brian Foote and Joseph Yoder described it in Big Ball of Mud (1997) as the most common architecture in practice. It rarely starts that way: deadlines, turnover and quick fixes slowly erase the borders, until a database table is written by ten modules and a change to pricing breaks login.
A rewrite from scratch is tempting and usually the riskiest option. The safer path is to find seams, draw a context map of what is really there, and move one area at a time with the strangler fig pattern, first into a modular monolith or separate services. Splitting the mud into services without fixing the borders gives you a distributed monolith.
Sources
- Brian Foote, Joseph Yoder: Big Ball of Mud laputan.org
Related terms
- Technical debt: Shortcuts in code and design that speed up delivery now and make every later change slower until they are paid back.
- Strangler fig pattern: Replacing a legacy system piece by piece, routing one feature at a time to new code until the old system can be switched off.
- Modular monolith: One deployable application split inside into modules with clear boundaries, each owning its data and using the others only through defined interfaces.
- Distributed monolith: Services that look separate but have to be changed, tested and deployed together, so you pay for microservices and still have a monolith.
- Context map (DDD): A diagram of the bounded contexts in a system and the kind of relationship between each pair: who depends on whom and how models are translated.
