Rohit M S
Rohit M S is an AWS Certified Solutions Architect and DevOps/Backend Engineer with over 8 years of experience building and automating cloud infrastructure. His expertise spans the full DevOps lifecycle — CI/CD pipeline design with Jenkins, GitHub, Docker, and Kubernetes, plus infrastructure-as-code using Terraform and Ansible across AWS and Azure. He has architected highly available, fault-tolerant systems using EC2, EKS, Lambda, S3, and DynamoDB, alongside monitoring solutions built on Prometheus and Grafana.
Beyond infrastructure engineering, he has hands-on experience with IoT data pipelines, microservices communication architecture, and distributed computing research. His technical foundation includes strong programming in Core Java, C/C++, and Python, backed by an MTech in Engineering.
Earlier in his career, he independently built and led an education-sector automation platform, and separately engineered an algorithmic trading system using technical indicators like RSI and EMA — reflecting a builder's mindset spanning both enterprise infrastructure and entrepreneurial product work.
Session
Observability platforms like DataDog deliver excellent out-of-the-box experience, but at scale their per-host, per-GB, and per-trace pricing can balloon into one of the largest line items in an infrastructure budget. This talk walks through how we replaced DataDog end-to-end with a fully open-source stack — Prometheus for metrics, Loki with Promtail for log aggregation, Jaeger for distributed tracing, and Grafana as the unified visualization and alerting layer — without compromising on the three pillars of observability. I'll cover the real architecture we ran in production: how the pieces fit together, the ingestion and storage trade-offs versus a managed SaaS product, and the migration path from existing DataDog dashboards and alerts. I'll also be candid about where open source falls short of DataDog (correlation across signals, out-of-the-box APM magic, support SLAs) and how we worked around those gaps. Attendees will leave with a practical blueprint for evaluating whether a self-hosted LGTM-style stack makes sense for their org, along with real cost and operational trade-offs from running it at scale.