Tiger Data × Axpo
Tiger Data x Axpo: From crashed database to 150M rows a day
150 million rows ingested per day from 20+ power plants
System crashed at two plants to stable ingest at 20+ plants
Members read free
Unlock the full breakdown
Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.
Free. No spam. Unsubscribe anytime.
You're in — enjoy the library.
Why it works
The before-state is vivid and specific: a named database crashed after filling up with data from only two plants, giving the reader a concrete failure to measure recovery against. The story layers two distinct migrations, SQL Server to TimescaleDB then MST Azure to Tiger Cloud, which makes the technical reasoning credible and shows the team making deliberate architectural choices rather than chasing hype. The mechanism explanation, hypertable partitioning, LTTB downsampling, tiered S3 storage, is detailed enough that an engineer could replicate the approach.
Steal this
The double-migration narrative structure: showing a first failed fix before the final solution makes the vendor's differentiation (storage independent of compute) concrete and earned rather than asserted.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are Tiger Data's published work; we link to the source and lead with our analysis.