Backend engineer based in India 🇮🇳. I learn by building production-grade systems end to end — writing the service, containerizing it, wiring the CI/CD, deploying it, load-testing it, and keeping it observable. Right now I'm pushing deeper into distributed systems, platform / SRE, and AI infrastructure.

I contribute to the infrastructure I run — nine distinct changes merged across seven projects (all merged PRs). The ones worth reading:

• Grafana Mimir — store-gateway leaked one TCP connection per get_range because loadChunks closed the bucket range reader without draining it, so net/http discarded the connection instead of pooling it. Root-caused from a user's connection-exhaustion report and fixed by draining before close.
• Argo CD — a fix for operationState carrying values from a failed sync attempt landed on master, but the cherry-pick bot failed minutes later, so every supported release still shipped the bug. After two independent reports against released versions I carried it back to 3.3, 3.4 and 3.5 by hand.
• KubeRay — killing kubectl ray session by PID left its kubectl port-forward child reparented to init, still holding all four listeners. The dashboard kept answering 200 after the session was gone and the next session couldn't bind.
• Grafana Mimir — max-connections-per-host reads as a process-wide cap, but the limit lives on one bucket client's transport, so a process running several components opens a multiple of it. Measured 29 concurrent connections against a configured 25 to prove more than one transport was live.
• Grafana Mimir — the Kafka Helm chart mounted its data claim one directory above KAFKA_LOG_DIRS, so containerd satisfied the image volume instead and the claim went unused.

Plus Traefik, KEDA and Thanos — a Redis provider requirement that silently breaks when unset, a Temporal deprecated-API removal, and a link check that had been failing every PR for two weeks.

Currently open across Envoy Gateway, Argo Workflows, Cilium, Thanos, Dapr, Postgres Operator, KubeRay and Traefik.

driftlab — Jepsen asks whether a server keeps its promises. driftlab asks whether the client library you import keeps its documented delivery guarantees under faults. A driver per library/version records a JSONL history in Jepsen's vocabulary; a pure offline checker reports lost-write, poll-skip, non-monotonic poll, duplicate, stall and phantom. Calibrated against a known NATS regression so a clean run on the fixed version proves the harness actually bites. Two findings reported upstream so far: nats.go 2180 and 2181.

chat-go — real-time chat in Go. WebSocket gateway with Redis pub/sub fan-out, Kafka as the durable log feeding three independent consumer groups (history, pgvector search indexing, local-LLM RAG bot), Postgres + pgvector, and streaming catch-up summaries over the socket. Includes a hardening write-up and a documented scaling limit I left in deliberately.

news-feed-go — production-grade news feed in Go: auth, post CRUD, a follow graph, hybrid push/pull fan-out, ranking, Redis cache-aside, pgvector semantic search, notifications and full observability. Built as a real system rather than a toy MVP.

StudentSystemGo — a Go REST API layered all the way up to production as a system-design playground:

• Multi-stage Docker build · GitHub Actions CI/CD to AWS EC2, later redeployed on K3s
• Nginx load balancer across multiple app instances with circuit breaking
• MySQL primary + replica with read/write split · Redis rate limiting + cache-aside
• S3 + CloudFront media storage provisioned with Terraform
• RabbitMQ worker queue · Prometheus metrics · k6 load tests
• Deep-dive docs covering architecture, deployment, observability & load testing

• driftlab, next — a Kafka driver alongside the NATS one, so the same checker runs against two ecosystems and the anomaly vocabulary has to hold up in both.
• Distributed systems via MIT 6.5840 — MapReduce ✅ · KV server + lock ✅ · Raft in progress.
• chat-go, next phase — presence and multi-gateway coordination, then WebRTC for voice/video across real networks, with a TURN relay and a measured connection success rate.
• GitOps homelab on K3s + ArgoCD — moving my self-hosted services to declarative, Git-driven deployments.

Backend today → distributed systems and platform / SRE. Same throughline everywhere: own systems end-to-end, and bring that rigor to the infrastructure that runs AI. Next on the roadmap — Raft carried through to a working consensus implementation, and an internal developer platform built around a credential broker and a blast-radius engine rather than a service catalogue.

Languages

Backend & Data

Infra & DevOps

Observability & Testing

• 💼 LinkedIn — omkar-shendge
• 📧 Email — omkarshendge619@gmail.com
• 🐦 X / Twitter — @p0pobeast