👋 Hi, I’m Sagar

Senior Backend Engineer with 6+ years of experience designing and operating backend systems, microservices, and distributed architectures.

I focus on building reliable, observable, and scalable systems, with a strong interest in:

• Distributed systems & messaging
• Service-to-service communication (gRPC)
• Observability & production readiness
• System design trade-offs

I enjoy going deep into why systems behave the way they do, not just how to wire them together.

Featured Project

🔎 reqlog — Trace requests across services & Docker logs (Golang)

A lightweight CLI tool to trace requests across multiple services, files, and Docker containers using key/value search (e.g. request_id, trace_id).

• Built in Go for speed and simplicity
• Supports file logs + Docker logs (multi-source tracing)
• Enables fast request tracing during production incidents
• Used by my team in real debugging workflows
• Includes filtering, follow mode, and multi-source search

👉 Built to solve real-world debugging pain in distributed systems
👉 Personally used it to significantly reduce time to trace requests across services

Core Expertise

• Languages: Go, Node.js (TypeScript)
• Backend & APIs: gRPC, REST, NestJS
• Datastores: PostgreSQL, Redis
• Messaging: RabbitMQ (AMQP), Event-Driven systems
• Infrastructure: Docker, Kubernetes (KIND), AWS
• Observability: Prometheus, Grafana, Loki, Jaeger, OpenTelemetry
• Architecture: Microservices, Async workflows, Idempotency, Retries, Backoff, Graceful Shutdowns

Writing & Knowledge Sharing

I actively write about real-world backend and distributed systems topics, with a strong focus on production correctness, failure handling, and operational trade-offs.

Selected Articles:

• Transactional Outbox with RabbitMQ (Series)

  • Reliable event publishing from relational databases
  • Retry strategies, backoff, and dead-letter queues
  • Consumer-side reliability and observability
  • Designing for at-least-once delivery and idempotency

• Understanding gRPC Client-Side Load Balancing with DNS

  • gRPC name resolution
  • Client-side load balancing trade-offs
  • Practical production considerations

• Designing Go Microservices (Series)

  • Project structure, configuration, structured logging
  • gRPC servers, graceful shutdowns, Docker & Makefiles
  • PostgreSQL integration, Redis caching
  • Prometheus metrics, OpenTelemetry tracing, health checks

I share shorter insights and architecture diagrams on LinkedIn, and deeper technical write-ups on dev.to.

What I Care About

• Clean architecture & clear service boundaries
• Failure handling (timeouts, retries, idempotency)
• Production observability before “pretty dashboards”
• Systems that fail predictably, not silently
• Long-term maintainability over short-term hacks

Looking Ahead

I’m interested in senior backend / distributed systems roles with:

• Strong engineering culture
• Real production scale
• Emphasis on correctness, reliability, and learning
• Remote-first or relocation-friendly environments (EU / global)

Find Me

• LinkedIn: https://www.linkedin.com/in/sagarmaheshwary/
• dev.to: https://dev.to/sagarmaheshwary
• GitHub: You’re already here 🙂