Field notes
Practical writing on microservices boundaries, measurement, and the decisions teams put off.
Notes from consulting floors and remote sessions — written for engineers and managers who already live with the systems discussed.
When a shared database is the real service boundary
Why inventory, pricing, and warehouse teams keep blocking each other — and how to sequence ownership before you extract code.
Latency hunts that start with one customer journey
Why whole-estate profiling wastes the first week, and how to pick a journey that will teach you something shippable.
Workshop seating for boundary redraws
Who must be in the room when you redraw service domains — and who politely receives the notes afterward.
Reading failure modes before funding a platform year
What an architecture review should pressure-test when leadership wants a multi-quarter microservices programme.