DBMS > GeoMesa vs. LevelDB vs. Quasardb vs. RocksDB vs. TimescaleDB

System Properties Comparison GeoMesa vs. LevelDB vs. Quasardb vs. RocksDB vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Distributed, high-performance timeseries database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

www.geomesa.org

github.com/google/leveldb

quasar.ai

rocksdb.org

www.timescale.com

Technical documentation

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

github.com/google/leveldb/blob/main/doc/index.md

doc.quasar.ai/master

github.com/facebook/rocksdb/wiki

docs.timescale.com

Developer

CCRi and others

Google

quasardb

Facebook, Inc.

Timescale

Initial release

2014

2011

2009

2013

2017

Current release

5.0.0, May 2024

1.23, February 2021

3.14.1, January 2024

9.2.1, May 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

BSD

Open Source

Apache 2.0

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++

Server operating systems

Illumos
Linux
OS X
Windows

BSD
Linux
OS X
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP API

C++ API
Java API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

consistent hashing

horizontal partitioning

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Source-replica replication with selectable replication factor

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

by using LevelDB

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

Transient mode

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Cryptographically strong user authentication and audit trail

fine grained access rights according to SQL-standard

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.