Showing Post From Performance
MySQL-compatible databases in 2026: revisit MySQL, MariaDB and Percona Server before you upgrade another database
Most teams that run MySQL do not choose their database every year. They chose it once, long ago, and since then they have only upgraded it, or not upgraded it.
Read moreIn-process analytics in 2026: revisit DuckDB, Polars and chDB before you spin up another warehouse for a small question
Think of a knitwear exporter in Tiruppur that makes T-shirts, polos and kids’ wear for buyers in Europe, the US, the Gulf and Japan (an invented example, not a real client).
Read moreLoad testing in 2026: revisit Grafana k6, Locust and Gatling before you run another performance test
Picture a company in Lucknow that hosts exam results and admit cards for several state boards and universities across Uttar Pradesh and Bihar (an invented example, not a real client).
Read moreLog storage in 2026: revisit Grafana Loki, VictoriaLogs and OpenObserve before you keep another month of logs
Picture a platform team in Pune that runs a B2B lending stack for NBFCs across Maharashtra and Gujarat (an invented example, not a real client).
Read moreContinuous profiling in 2026: revisit Grafana Pyroscope, Parca and the OpenTelemetry eBPF profiler before you store another flame graph
Picture a GST invoicing SaaS in Pune with about 1,800 business customers (an invented example, not a real client). Its platform team of six runs about 40 services, mostly Go with a few Java and Python ones, on a 12-node Kubernetes cluster.
Read moreDistributed tracing in 2026: revisit Jaeger, Grafana Tempo and SigNoz before you store another span
Picture a bus, train and hotel booking platform in Kochi (an invented example, not a real client). Customers book from an Android app, an iOS app and a web app.
Read more