DBMS > eXtremeDB vs. GeoMesa vs. MySQL vs. TerarkDB

System Properties Comparison eXtremeDB vs. GeoMesa vs. MySQL vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Natively in-memory DBMS with options for persistency, high-availability and clustering

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Widely used open source RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS
Time Series DBMS

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#100	Relational DBMS
	#18	Time Series DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

www.mcobject.com

www.geomesa.org

www.mysql.com

github.com/bytedance/terarkdb

Technical documentation

www.mcobject.com/docs/extremedb.htm

www.geomesa.org/documentation/stable/user/index.html

dev.mysql.com/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

McObject

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

ByteDance, originally Terark

Initial release

2001

2014

1995

2016

Current release

8.2, 2021

5.0.1, July 2024

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted open source version available

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.

Implementation language

C and C++

Scala

C and C++

C++

Server operating systems

AIX
HP-UX
Linux
macOS
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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.

support of XML interfaces available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

yes

with proprietary extensions

APIs and other access methods

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

Supported programming languages

.Net
C
C#
C++
Java
Lua
Python
Scala

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

C++
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

by defining events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning / sharding

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

depending on storage layer

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

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

Optimistic (MVCC) and pessimistic (locking) strategies available

yes

table locks or row locks depending on storage engine

yes

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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.