DBMS > GeoMesa vs. RocksDB vs. Spark SQL vs. Tigris

System Properties Comparison GeoMesa vs. RocksDB vs. Spark SQL vs. Tigris

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.

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Spatial DBMS

Key-value store

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

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

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

Technical documentation

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

github.com/facebook/rocksdb/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

www.tigrisdata.com/docs

Developer

CCRi and others

Facebook, Inc.

Apache Software Foundation

Tigris Data, Inc.

Initial release

2014

2013

2014

2022

Current release

5.0.0, May 2024

9.2.1, May 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

Open Source

Apache 2.0

Open Source

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

Scala

Server operating systems

Linux

Linux
OS X
Windows

Linux
macOS
Windows

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

SQL-like DML and DDL statements

APIs and other access methods

C++ API
Java API

JDBC
ODBC

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

Java
Python
R
Scala

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

none

yes

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

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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

Access rights for 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.