Blog
Original writing on architecture, event-driven systems, reliability and engineering careers — drawn from production work on banking and high-traffic platforms, with the numbers and the trade-offs left in.
14 articles
Seven years from Software Engineer R&D to Lead Product Engineer, and the three things that actually moved it: learning on a structured path instead of by accident, taking ownership of problems nobody assigned, and understanding the product rather than just my service.
Notes from building and hardening an API gateway handling 5M+ requests a day at 99.95% availability: the failure modes that do not show up until real traffic, and the patterns that actually held.
A deploy is not an event, it is a dial you turn. Building a canary framework with feature flags and A/B testing that cut deployment incidents 70% and doubled release velocity — and why the promotion gate matters more than the rollout mechanism.
Principles do not cut defect rates. Agreement about where behaviour belongs does. How mentoring 10+ engineers into consistent SOLID and CQRS adoption cut defect leakage 40%, and why most of that work was not technical.
Banking data arrives as files on somebody else's schedule and has to be processed as a stream with money-grade correctness. Why the ingest tool and the event backbone are different tools, and what a distributed cache is genuinely for.
Building analytics that answer questions about the last five minutes, not last night: windowing and the late-event problem, why the state store needs a changelog topic, and the split between what Kafka Streams should compute and what Elasticsearch should.
