DBMS > GeoSpock vs. IBM Db2 Event Store vs. MySQL vs. SQream DB vs. Tarantool

System Properties Comparison GeoSpock vs. IBM Db2 Event Store vs. MySQL vs. SQream DB vs. Tarantool

Editorial information provided by DB-Engines

Name

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

Description

Spatial and temporal data processing engine for extreme data scale

Distributed Event Store optimized for Internet of Things use cases

Widely used open source RDBMS

a GPU-based, columnar RDBMS for big data analytics workloads

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Event Store
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

geospock.com

www.ibm.com/products/db2-event-store

www.mysql.com

sqream.com

www.tarantool.io

Technical documentation

www.ibm.com/docs/en/db2-event-store

dev.mysql.com/doc

docs.sqream.com

www.tarantool.io/en/doc

Developer

GeoSpock

IBM

Oracle

since 2010, originally MySQL AB, then Sun

SQream Technologies

Initial release

2017

1995

2017

2008

Current release

2.0, September 2019

2.0

8.4.0, April 2024

2022.1.6, December 2022

2.10.0, May 2022

License

Commercial or Open Source

commercial

free developer edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++, CUDA, Haskell, Java, Scala

C and C++

Server operating systems

hosted

Linux

Linux, macOS, Windows for the developer addition

FreeBSD
Linux
OS X
Solaris
Windows

Linux

BSD
Linux
macOS

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

string, double, decimal, uuid, integer, blob, boolean, datetime

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

through the embedded Spark runtime

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

.Net
JDBC
ODBC

Open binary protocol

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

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

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions in Python

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal and vertical partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

Multi-source replication
Source-replica replication

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

not for MyISAM storage engine

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.