DBMS > Citus vs. HarperDB vs. Kingbase vs. MySQL vs. PostGIS

System Properties Comparison Citus vs. HarperDB vs. Kingbase vs. MySQL vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Widely used open source RDBMS

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Document store

Document store
Spatial DBMS

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.50
Rank	#257	Overall
	#119	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

Technical documentation

docs.citusdata.com

docs.harperdb.io/docs

dev.mysql.com/doc

postgis.net/documentation

Developer

HarperDB

BeiJing KINGBASE Information technologies inc.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2010

2017

1999

1995

2005

Current release

8.1, December 2018

3.1, August 2021

V8.0, August 2021

8.4.0, April 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

free community edition available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Node.js

C and Java

C and C++

Server operating systems

Linux

Linux
OS X

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-like data manipulation statements

Standard with numerous extensions

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Custom Functions

since release 3.1

user defined functions

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

horizontal partitioning (by range, list and hash) and vertical partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes

the nodes on which a table resides can be defined

yes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Atomic execution of specific operations

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.