DBMS > BoltDB vs. GeoMesa vs. KairosDB vs. MySQL vs. SAP HANA

System Properties Comparison BoltDB vs. GeoMesa vs. KairosDB vs. MySQL vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Distributed Time Series DBMS based on Cassandra or H2

Widely used open source RDBMS

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/boltdb/bolt

www.geomesa.org

github.com/kairosdb/kairosdb

www.mysql.com

www.sap.com/products/hana.html

Technical documentation

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

kairosdb.github.io

dev.mysql.com/doc

help.sap.com/hana

Developer

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

SAP

Initial release

2013

2014

2013

1995

2010

Current release

4.0.5, February 2024

1.2.2, November 2018

8.4.0, April 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

Scala

Java

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Data scheme

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

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

proprietary syntax

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

based on Cassandra

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

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

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

simple password-based access control

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.