Arun Balachandran
← Work

In progress · Jun 2026 —

Microservices consolidation

Everyone knows how to split a monolith. Far fewer people write down what to do when the split went too far.

Role
Sole researcher and engineer
Stack
Python, Docker, Kubernetes
Status
Measuring; writing next
Links
Repository
Architecture diagram or dashboard shot goes here

The problem

Two or three paragraphs on the situation and why the obvious answer was wrong. Keep it concrete — a number, a failure, a constraint.

What I did

The work itself. Decisions and trade-offs, not a tour of the tech stack.

What came out of it

Results, and the part that did not work. The second half is what makes the first half believable.