Compaction without surprises

Hidden behavior

Compaction is easy to treat as implementation detail until it shows up in latency. Then it stops feeling hidden very quickly. The systems that age well are the ones where maintenance work is part of the design conversation from the beginning.

Operational intuition

When you understand where write amplification and read amplification come from, you start designing application workloads more honestly. That usually leads to better expectations and fewer mysterious incidents.