DBMS > GeoMesa vs. IBM Db2 Event Store vs. KairosDB vs. VoltDB

System Properties Comparison GeoMesa vs. IBM Db2 Event Store vs. KairosDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed Event Store optimized for Internet of Things use cases

Distributed Time Series DBMS based on Cassandra or H2

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Spatial DBMS

Event Store
Time Series DBMS

Time Series DBMS

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.geomesa.org

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

github.com/kairosdb/kairosdb

www.voltdb.com

Technical documentation

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

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

kairosdb.github.io

docs.voltdb.com

Developer

CCRi and others

IBM

VoltDB Inc.

Initial release

2014

2017

2013

2010

Current release

5.0.0, May 2024

2.0

1.2.2, November 2018

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free developer edition available

Open Source

Apache 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Scala

C and C++

Java

Java, C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux
OS X
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

Java
JavaScript

Node.js
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Active-active shard replication

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

Data access is serialized by the server

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

Snapshots and command logging

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

simple password-based access control

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Advancements in streaming data storage, real-time analysis and machine learning
25 July 2019, IBM

How IBM Is Turning Db2 into an 'AI Database'
3 June 2019, Datanami

Best cloud databases of 2022
4 October 2022, ITPro

provided by Google News

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

Expo: Real Time A/B Testing and Monitoring with Spark Streaming and Kafka at Walmart Labs
24 May 2019, InfoQ.com

provided by Google News

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

VoltDB Aims for Fast Big Data Development -- ADTmag
29 January 2015, ADT Magazine

provided by Google News

Share this page