Kranti
Go, distributed systems, game servers
I design and build backend systems in Go: services that talk over gRPC and message queues, own their data, and stay honest about failure. Most of what I know I learned by building it, breaking it, and writing down why.
- GitHubgithub.com/darkphotonKN
- Productivity platformFireplaceGo · gRPC · PostgreSQL
A Go monolith being pulled apart into gRPC services behind an HTTP gateway, one slice at a time. Per-service Postgres, RabbitMQ events through a transactional outbox, and a generated OpenAPI contract with breaking-change gates.
Go · gRPC · PostgreSQL · RabbitMQ · Redis · Next.js
1 post on this → - Multiplayer gameBarrowspireGo · ECS · WebSockets
A real-time 2D multiplayer game with an authoritative Go server built on an entity component system, backed by services for characters, items, a marketplace, a ledger and payments.
Go · ECS · WebSockets · gRPC · PostgreSQL · Phaser
1 post on this → - AI engineering workflowSkill fleetClaude Code · Markdown · Git
Twenty-four agent skills that run a spec-anchored development workflow across several repos: scope, spec, slice into issues, build test-first, review against the spec, audit for drift.
Claude Code · Markdown · Git
- Diagramming boardQuantaGo · PostgreSQL · Next.js
A dark, full-screen whiteboard for freehand sketches, boxes, arrows and text, built around a pristine drawing experience. Go monolith with a Next.js canvas.
Go · PostgreSQL · Next.js · Canvas
- Languages
- Go · TypeScript · SQL
- Services
- gRPC and protobuf · REST with OpenAPI · WebSockets · Event-driven with RabbitMQ
- Data
- PostgreSQL · Redis · Transactional outbox · Migrations
- Platform
- Docker · Consul · OpenTelemetry
- Frontend
- Next.js · React · Tailwind
Roles, dates and the rest of the CV go here next.