A modular monolith without enforcement is not an architecture — it is a monolith with good...
A modular monolith without enforcement is not an architecture — it is a monolith with good intentions.
The Problem
Most teams skip the modular monolith and jump straight to microservices. The ones that do attempt a modular monolith rely on convention — "don't cross module boundaries" — which fails the moment deadlines hit.
The difference between a well-structured modular monolith and a mess is whether boundaries are maintained by tooling or by convention.
The Solution Structure
Throughout my career, transitioning between CTO roles and, more recently, focusing purely on...
In the last part, we talked about why we built Vyshyvanka. Today, we're going to talk about how....
A Rails app grows. Changes in one corner start breaking another, two teams keep colliding in the same...
Why boundaries (module structure, clean interfaces, and strict types) are the single most important...
Stop Fixing Broken Architecture: Auto-Enforce Package Boundaries with Cursor Composer and...
I’ve spent way too many late nights arguing about whether a "legacy" monolith is actually the problem...
