The Bug That Only Showed Up After a Week: Why We Still Needed to Add a Daily VACUUM
Part 3 of 3 — A Quieter Story About Ongoing Ownership
This blog is a behind-the-scenes look at building and scaling industrial intelligence systems at Kompress.ai.
We write about what happens when software meets real machines in the field where latency, reliability, and scale are not theoretical problems, but daily constraints.
Part 3 of 3 — A Quieter Story About Ongoing Ownership
The partition index table, the monitoring system, and reading the sawtooth
Four days after hitting 0.00000% droppable tombstones on all three nodes simultaneously — the cleanest state the cluster had ever been in — the Slack report showed 30% again
Migrating 3.9 Billion Rows to TWCS Without Downtime on a Constrained IoT Cluster The number that started everything was 7.99 ms. That was the average read latency on our Cassandra keyspace — a cluster

Part 2 of 2 — Two Swap Cycles, One Rollback, and Why the Safety Net Made All the Difference
Part 1 of 2 — The Problem, The Design, The Migration
Which LLM should you use? That’s usually the first question. But after building real-world AI systems, we realized something: 👉 The model matters. 👉 The design of interaction matters more. Most

Most people celebrate growth. We at kompress.ai learnt to read it carefully. Over the last 12 months, we tracked a simple metric: daily telemetry requests from devices deployed in the field. This is r