vs

KingbaseES vs Tibero

KingbaseES: Chinese PostgreSQL-derived RDBMS with Oracle, MySQL and SQL Server compatibility modes. Tibero: Korean Oracle-compatible RDBMS with RAC-style Active Cluster, popular for Oracle exits in Asia.

key differences

  • Only KingbaseES has full-text search, json.
  • Only Tibero has compression.

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

choose tibero for

  • +Replacing Oracle Database in public-sector systems
  • +Banking and insurance core systems in Korea
  • +Lowering licence cost for Oracle-style applications

best at · OLTP, Warehouse

overview
Primary model
Relational
Relational
Also supports
Document
–
Type
Database engine
Database engine
Status
Active
Active
Developer
CETC Kingbase (中电科金仓)
TmaxTibero
First release
1999
2003
Latest version
V9R4C11 (Feb 2025)
7.2.6 (2026)
License
ProprietaryProprietary commercial license
ProprietaryProprietary commercial license
Free tier
—
—
popularity
WhichDB Score
0.0
0.8
Rank
#764
#613
GitHub stars
–
–
Stack Overflow questions
–
10
scale & guarantees
Comfortable data size
Medium (≤ 10 TB)
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
Client server, Shared storage, Primary replica
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, PL/SQL-compatible procedural SQL, PL/pgSQL
SQL, tbPSM (PL/SQL-compatible)
Client languages
Java, C, C#, Python, Go
Java, C, C#, Python
Best for
OLTP, Warehouse
OLTP, Warehouse

KingbaseES vs Tibero: FAQ

What is the difference between KingbaseES and Tibero?

KingbaseES: Chinese PostgreSQL-derived RDBMS with Oracle, MySQL and SQL Server compatibility modes. Tibero: Korean Oracle-compatible RDBMS with RAC-style Active Cluster, popular for Oracle exits in Asia. Only KingbaseES has full-text search, json. Only Tibero has compression.

When should I choose KingbaseES over Tibero?

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. Choose Tibero for replacing Oracle Database in public-sector systems; banking and insurance core systems in Korea; and lowering licence cost for Oracle-style applications.

Is KingbaseES or Tibero more popular?

Tibero ranks #613 on the WhichDB Score (0.8/100) and KingbaseES ranks #764 (0.0/100). Popularity is not fit: check the requirements that matter for your project.

Are KingbaseES and Tibero open source?

No. KingbaseES is proprietary, closed-source software. No. Tibero is proprietary, closed-source software.