Rebuilding a Platform Under Itself: Monolith to Microservices Without Stopping the Business
Notes from a live V2→V3 re-platforming, moving a tightly-coupled Node/Python duolith to Laravel microservices while the old system keeps serving customers.
cto & full-stack engineer
I lead technology at CapStellar, a digital-assets platform — architecture, security, and applied AI. Here I write about engineering practices, automation, and system architecture.
Notes from a live V2→V3 re-platforming, moving a tightly-coupled Node/Python duolith to Laravel microservices while the old system keeps serving customers.
Why I built our operations console instead of buying one, and the design rules that keep it trustworthy: read-only collectors, flap-resistant alerting, and a dead-man’s switch.
How we gave a Laravel API a warm standby on another continent with a Cloudflare Load Balancer, a read replica, and a short list of deliberate rules. It is not active-active, and that’s the point.
How a Tailscale mesh turned servers on four hosting providers into one private network, and the operational rules that keep it clean: tags, key expiry, explicit public holes.