Architecture thinking
Does the monolith really need to be split?
Deployment, testing, fault tolerance, and scaling: the problems that can justify splitting a monolith, and the costs to weigh before doing it.
Notes from production
Practical thinking about architecture, distributed systems, and the decisions that shape reliable software.

Latest writing
Deployment, testing, fault tolerance, and scaling: the problems that can justify splitting a monolith, and the costs to weigh before doing it.
I weigh deployment independence, failure risks, and maintenance costs to decide which static and dynamic dependencies I'm willing to own.
What you will find here
Failure modes, recovery paths, and lessons from running systems.
The cost of a decision matters as much as its benefits.
Systems should remain understandable as they grow.