Showing Post From Performance
Lakehouse table formats in 2026: revisit Apache Iceberg, Delta Lake and Apache Hudi before you pick another format
Picture a payments and lending analytics platform in Hyderabad (an invented example, not a real client). Card authorisations and EMI schedules still land in PostgreSQL 16.
Read moreReal-time OLAP in 2026: revisit ClickHouse, Apache Doris and StarRocks before you build another dashboard warehouse
Picture an ecommerce and last-mile logistics platform in Bengaluru (an invented example, not a real client). Order capture and inventory still run on PostgreSQL 16.
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 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 morePgBouncer and its alternatives: revisit your PostgreSQL connection pooler
A team runs about forty services on Kubernetes against one PostgreSQL primary. During a sale, the autoscaler adds pods, each opens its own pool of ten connections, and PostgreSQL starts refusing logins with “remaining connection slots are reserved”.
Read moreRedis, Valkey, and Dragonfly clients: revisit your connection settings before the next failover
An order service runs on Valkey with Sentinel. At 2 AM the team runs a planned failover before patching the primary.
Read more