AI Agents Are Distributed Systems. We Just Gave the Problem a New Name.Every production failure you'll hit building AI agents — lost state, duplicate side effects, cascading crashes, runaway costs — was solved by distributed systems engineers before most agent frameworks11KJul 12 · 9 min readravilanka.hashnode.dev
Your Business Logic is Hostage to Your DatabaseHow to Read This Article (Important) This is a long-form architectural deep dive, not a quick tutorial. You'll get the most value if you read it in order: Part I explains why distributed systems force replay and why impurity becomes dangerous Part ...Jan 16 · 22 min readravilanka.hashnode.dev
What if Your Code Could Survive Any Crash? (It Can)TL;DR In Part 1, we identified the problem: 60-80% of microservice code is infrastructure. Retries, state machines, idempotency, distributed locks. This post introduces durable execution: the runtime journals every step of your code. Crash mid-execut...Jan 11 · 25 min readravilanka.hashnode.dev
I Deleted 500 Lines of Infrastructure Code. Nothing Broke.TL;DR Most microservice codebases are 60-80% infrastructure, 20-40% business logic. We call this the "glue code tax"—and it's killing engineering velocity. This series shows you how to eliminate it. The Audit That Changed Everything Last month, I ...Jan 4 · 7 min readravilanka.hashnode.dev