How We Survived
Actionbase was deployed to production before it was “complete.” It had to keep evolving while maintaining production contracts.
Tests passed. But we couldn’t confidently answer “is there really no problem?” We walked along streams in Pangyo (Tancheon and Unjungcheon) discussing this concern. How could we build a state where even we could trust the system?
So we built verification layers.
Verification Layers
Section titled “Verification Layers”| Stage | Method | Purpose |
|---|---|---|
| Dev | Tests as Contracts | Define and protect promised behaviors |
| Pre-Deploy | Shadow Testing | Verify new versions with production traffic |
| Migration | Comparison Verification | Confirm Source DB and Actionbase data match |
| Runtime | HBase Consistency | Maintain consistency between State, Index, Count |
Each layer catches different types of problems. One layer isn’t enough.
What We Gained
Section titled “What We Gained”Through verification, we gained confidence: even if issues occur, we can detect and correct them.
As this confidence accumulated, we could trust Actionbase even when it was the ledger itself. This wasn’t a design decision made upfront. It was trust earned by building verification.
The goal isn’t to prevent all failures. It’s to detect and fix them before they matter.