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

Terraform and OpenTofu pull requests in 2026: revisit Atlantis, OpenTaco and Stategraph before you run another apply from a laptop

Most infrastructure teams know this Friday evening. A developer runs terraform apply from a laptop because “it is a small change”.

Read more

Kubernetes multi-tenancy in 2026: revisit vCluster, Capsule and Kamaji before you hand another team its own cluster

Sooner or later a platform team gets the same request again. A product squad wants “its own cluster” because it needs to install an operator with cluster-scoped CRDs, a data team wants admin rights to try a new scheduler, and a customer-facing team asks for hard isolation because an auditor said so.

Read more

Progressive delivery in 2026: revisit Argo Rollouts, Flagger and PipeCD before you ship another big-bang deploy

A Kubernetes RollingUpdate feels safe because pods come up gradually and readiness probes gate traffic. For many services that is still fine.

Read more

Data quality in 2026: revisit Great Expectations, Soda Core and Elementary before you trust another dashboard number

When a dashboard loads and the chart looks clean, many teams treat the number as truth. The next habit is worse: if finance, sales and product argue about different figures, somebody opens a spreadsheet and “fixes” the number by hand for the meeting.

Read more

Kubernetes cost visibility in 2026: revisit OpenCost, Kubecost and Robusta KRR before you buy another FinOps tool or add another node

When the cloud bill jumps, many teams reach for one of two habits. The first is to add another node because some pods are Pending and nobody wants an outage.

Read more

ML experiment tracking in 2026: revisit MLflow, Aim and ClearML before you buy another hosted tracker seat

Many ML and LLM teams still treat a hosted experiment tracker as the adult default. A few notebook charts feel messy, someone pastes a Weights & Biases or Neptune signup link into Slack, and the team buys another seat before anyone asks where the run history, artefacts and model lineage must live.

Read more