Four Steps That Cut a Database Shortlist from 11 to 2
Any team facing a crowded database market can apply the same order: align constraints before comparing features. The compliance gate is specific to China's domestic IT push, but the principle of turning regulatory and operational reality into hard filters translates to any sector.
Database selection usually begins with a feature comparison table, but that approach led nowhere for a team picking a domestic replacement for its core system. After two weeks of benchmarking eleven products, the team switched to a four-step method that evaluates internal constraints first. Step one audits the source systems—Oracle, MySQL, and SQL Server—to define which compatibility details matter, from PL/SQL packages to system packages. Step two sizes the data: 3.2TB and under 4,000 concurrent connections place it squarely in centralized territory, despite industry numbers that push distributed adoption to 71% by 2026.
Step three applies a hard compliance gate for government and state-owned enterprise clients: Xinchuang certification, national cryptography algorithms, domestic CPU and OS support, cutting the list to five. Step four assesses the operational team—two DBAs with no distributed experience—making toolchain completeness and failover automation more valuable than raw performance. The surviving two candidates then go through a rigorous POC: top production SQL, migration assessment tools, mirrored traffic stress tests, failover drills, and hands-on DBA exercises.
The final pick, KingbaseES, passes all four steps. The method's core lesson is order: constraints decide what you can even consider, and the final comparison only ever involves two or three viable products.
Comparing features before aligning constraints wastes months; the team's initial half-month effort produced no decision, while the four-step method took three months to signing.
Compliance can eliminate more products than technology comparison; the technical merits of non-compliant products are irrelevant in government-facing projects.
The industry's 71% distributed adoption figure is skewed by new write-heavy IoT and edge workloads, which obscures the large centralized base in core transaction systems.
POC design changes the outcome: using production traffic and real DBA operations reveals operational fit that benchmarks and sales slides cannot.