DBMS > EventStoreDB vs. GeoSpock vs. MySQL vs. SpaceTime vs. XTDB

System Properties Comparison EventStoreDB vs. GeoSpock vs. MySQL vs. SpaceTime vs. XTDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Spatial and temporal data processing engine for extreme data scale

Widely used open source RDBMS

SpaceTime is a spatio-temporal DBMS with a focus on performance.

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Event Store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.eventstore.com

geospock.com

www.mysql.com

www.mireo.com/spacetime

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

developers.eventstore.com

dev.mysql.com/doc

www.xtdb.com/docs

Developer

Event Store Limited

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

Mireo

Juxt Ltd.

Initial release

2012

1995

2020

2019

Current release

21.2, February 2021

2.0, September 2019

8.4.0, April 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

MIT License

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

Java, Javascript

C and C++

C++

Clojure

Server operating systems

Linux
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

A subset of ANSI SQL is implemented

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

HTTP REST
JDBC

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

C#
C++
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Fixed-grid hypercubes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Real-time block device replication (DRBD)

yes, each node contains all data

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

Transaction concepts

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

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, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users can be defined per table

Users with fine-grained authorization concept

no user groups or roles

yes

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.