How Sprig Replaced Postgres, ClickHouse & Redis…with 4-8x Better Latency

This post details Sprig's migration from Postgres, ClickHouse, and Redis to ScyllaDB. It outlines the challenges faced with their initial relational database setup due to rapid growth (1.3T events, 75B attributes), the limitations encountered with Aurora Postgres (write throughput saturation, instance limits), and the subsequent adoption of ScyllaDB to achieve 4-8x better latency. The technical details focus on the data volume, event processing rate (20k-40k events/sec), and the need for low-latency decision-making for in-product surveys.