How the backend actually works: what I built, why it’s shaped that way, and what broke on the way.
I’m Kranti. I build Go services by day and keep building them after hours: a productivity app pulled apart into gRPC services, and a multiplayer game server. This is where the working notes go.
About me and my work →How Barrowspire's game-service turns a keypress into a velocity and a tick into one full snapshot per player, and the three places its goroutines share memory without agreeing who owns it.
I built a transactional outbox so plan-service could never lose an event and an inbox so insights-service could never process one twice, then never plugged them together.