DBMS > Amazon Aurora vs. BigObject vs. Kingbase vs. mSQL vs. MySQL

System Properties Comparison Amazon Aurora vs. BigObject vs. Kingbase vs. mSQL vs. MySQL

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Analytic DBMS for real-time computations and queries

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/rds/aurora

bigobject.io

www.kingbase.com.cn

hughestech.com.au/products/msql

www.mysql.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.bigobject.io

dev.mysql.com/doc

Developer

Amazon

BigObject, Inc.

BeiJing KINGBASE Information technologies inc.

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

1999

1994

1995

Current release

V8.0, August 2021

4.4, October 2021

8.3.0, January 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

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

C and Java

C and C++

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

Standard with numerous extensions

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

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

C
C++
Delphi
Java
Perl
PHP
Tcl

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

yes

Lua

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

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

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

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

Users with fine-grained authorization concept

no user groups or roles

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.