vs

Dameng (DM) vs KingbaseES

Dameng (DM): China's leading home-grown RDBMS; DM9 (2026) adds distributed, HTAP and AI features. KingbaseES: Chinese PostgreSQL-derived RDBMS with Oracle, MySQL and SQL Server compatibility modes.

key differences

  • Dameng (DM) is built for larger datasets (≤ 1 PB) than KingbaseES (≤ 10 TB).
  • Only Dameng (DM) has columnar storage, compression.

choose dameng for

  • +Replacing Oracle in government and state-owned enterprises
  • +Power-grid and energy management systems
  • +Financial back-office systems on domestic infrastructure

best at · OLTP, OLAP, HTAP

choose kingbase for

  • +Replacing Oracle in Chinese government systems
  • +Energy and utility enterprise applications
  • +Applications that must run on domestic Chinese hardware and OS

best at · OLTP, Warehouse

overview
Primary model
Relational
Relational
Also supports
Columnar / OLAP, Document
Document
Type
Database engine
Database engine
Status
Active
Active
Developer
Wuhan Dameng Database Co., Ltd.
CETC Kingbase (中电科金仓)
First release
1988
1999
Latest version
DM9 (Apr 22, 2026)
V9R4C11 (Feb 2025)
License
ProprietaryProprietary commercial license
ProprietaryProprietary commercial license
Free tier
✓
—
popularity
WhichDB Score
6.7
0.0
Rank
#355
#764
GitHub stars
–
–
Stack Overflow questions
–
–
scale & guarantees
Comfortable data size
Large (≤ 1 PB)
Medium (≤ 10 TB)
Horizontal scaling
Addon
Addon
Multi-region
Read replicas
Read replicas
ACID
Full
Full
Consistency
Strong
Strong
Schema
Strict
Strict
Architecture
Client server, Primary replica, Shared storage, Distributed
Client server, Primary replica, Shared storage
deployment
Self-hosted
✓
✓
Vendor-managed cloud
—
—
Serverless
—
—
Embedded
—
—
Edge
—
—
Clouds
–
–
capabilities
Transactions
✓
✓
Joins
✓
✓
Secondary indexes
✓
✓
Full-text search
✓
✓
Vector search
—
—
Geospatial
—
—
JSON
✓
✓
Change data capture
—
—
Triggers
✓
✓
Stored procedures
✓
✓
Materialized views
✓
✓
TTL / expiry
—
—
Pub/Sub
—
—
Columnar storage
✓
—
In-memory
—
—
Durable persistence
✓
✓
Compression
✓
—
Encryption at rest
✓
✓
Role-based access
✓
✓
Time travel
—
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
—
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
SQL, DMSQL (PL/SQL-compatible)
SQL, PL/SQL-compatible procedural SQL, PL/pgSQL
Client languages
Java, C, C#, Python, Go, PHP
Java, C, C#, Python, Go
Best for
OLTP, OLAP, HTAP, Warehouse
OLTP, Warehouse

Dameng (DM) vs KingbaseES: FAQ

What is the difference between Dameng (DM) and KingbaseES?

Dameng (DM): China's leading home-grown RDBMS; DM9 (2026) adds distributed, HTAP and AI features. KingbaseES: Chinese PostgreSQL-derived RDBMS with Oracle, MySQL and SQL Server compatibility modes. Dameng (DM) is built for larger datasets (≤ 1 PB) than KingbaseES (≤ 10 TB). Only Dameng (DM) has columnar storage, compression.

When should I choose Dameng (DM) over KingbaseES?

Choose Dameng (DM) for replacing Oracle in government and state-owned enterprises; power-grid and energy management systems; and financial back-office systems on domestic infrastructure. Choose KingbaseES for replacing Oracle in Chinese government systems; energy and utility enterprise applications; and applications that must run on domestic Chinese hardware and OS.

Is Dameng (DM) or KingbaseES more popular?

Dameng (DM) ranks #355 on the WhichDB Score (6.7/100) and KingbaseES ranks #764 (0.0/100). Popularity is not fit: check the requirements that matter for your project.

Are Dameng (DM) and KingbaseES open source?

No. Dameng (DM) is proprietary, closed-source software. No. KingbaseES is proprietary, closed-source software.