Showing Post From Operations
HTTP caching in 2026: revisit Varnish and Vinyl Cache, Apache Traffic Server and NGINX before you put another cache in front of your app
Most teams add an HTTP cache on a bad day. The home page is slow during a traffic spike, the database is at 100% CPU, and somebody says “let us just put Varnish in front”.
Read moreInfrastructure access in 2026: revisit Teleport, Boundary and Warpgate before you hand out another SSH key
Every engineering team has an access story it does not like to tell. A new developer joins, and someone appends her public key to authorized_keys on fourteen servers by hand.
Read moreBare-metal load balancers for Kubernetes in 2026: revisit MetalLB, kube-vip and Cilium LB IPAM before you expose another Service
On a cloud cluster, you write type: LoadBalancer in a Service and a minute later an IP address appears. On your own servers, the same line gives you a Service that sits in <pending> forever.
Read moreDistributed coordination in 2026: revisit etcd, ZooKeeper and Consul before you write another leader election
Most teams do not decide to build a distributed coordination system. It creeps in. A scheduled job runs on one VM.
Read moreAI gateways in 2026: revisit LiteLLM, Bifrost and Agent Router before you put another model API key in application code
Most teams did not plan their first AI gateway. It arrived as a side effect. One service called a hosted model with a key from an environment variable.
Read moreInfrastructure monitoring in 2026: revisit Zabbix, Checkmk and Netdata before you add another host to your monitoring
In most Indian companies, monitoring starts with a person, not a tool. Somebody in the IT team logs in to the file server every morning, checks the disk, looks at the UPS panel, pings the branch router, and goes back to work.
Read more