Featured Posts
Redis, Valkey, or Dragonfly: revisit the choice before you treat them as the same cache
If your service already uses Redis, the name on the port has not changed. The product behind that name has. Treating Redis, Valkey, and Dragonfly as three labels for one cache is the habit worth unlearning.
Read more
MongoDB 8.0 Performance is 36% higher, but there is a catch…
TLDR: If your app is performance critical, think twice, thrice before upgrading to MongoDB 7.0 and 8.0. Here is why…
Read more
Recent Posts
RabbitMQ, NATS and Kafka queues: revisit your message queue before you add another broker
A health insurance company in Hyderabad processes claims through RabbitMQ: three nodes on 3.13 with classic mirrored queues, about 40 lakh messages a day, from claim documents to OCR, OCR results to fraud checks and approvals to payments.
Read moreVector search in 2026: revisit pgvector, Qdrant, Milvus, Weaviate before you add a vector database
An e-commerce company in Pune runs customer support on PostgreSQL. The database holds about 2 million help articles, product Q&A threads and resolved tickets, in English and a fair amount of Hinglish.
Read moreService mesh in 2026: revisit Istio ambient, Linkerd and Cilium before you add sidecars
A logistics company in Bengaluru runs a production Kubernetes cluster with 14 nodes and about 420 pods. Three requests landed in one sprint.
Read moreKeycloak and its alternatives: revisit your identity provider before you standardise SSO
A SaaS company in Hyderabad runs Keycloak 24 on two virtual machines. It was set up in 2024 for about 60 internal tools and has worked quietly since.
Read moreArgo CD and Flux: revisit your GitOps controller before you scale or migrate
A platform team in Pune looks after 14 Kubernetes clusters. Most of them are managed by one central Argo CD instance that the team set up in 2021.
Read morePrometheus long-term storage: revisit Thanos, Mimir and VictoriaMetrics before you scale
A platform team runs two Prometheus servers per cluster as an HA pair, with 15 days of local retention. In one quarter, three requests arrive: the SRE lead wants a year of history for capacity planning, a product team adds a customer_id label to a request metric, and the auditors ask what happens to metrics when a disk dies.
Read more