DBMS > GeoMesa vs. Interbase vs. RocksDB vs. SQream DB

System Properties Comparison GeoMesa vs. Interbase vs. RocksDB vs. SQream DB

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.

Light-weight proven RDBMS

originally from Borland

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

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

Primary database model

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

www.geomesa.org

www.embarcadero.com/products/interbase

rocksdb.org

sqream.com

Technical documentation

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

docs.embarcadero.com/products/interbase

github.com/facebook/rocksdb/wiki

docs.sqream.com

Developer

CCRi and others

Embarcadero

Facebook, Inc.

SQream Technologies

Initial release

2014

1984

2013

2017

Current release

4.0.5, February 2024

InterBase 2020, December 2019

8.11.4, April 2024

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

BSD

commercial

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

Android
iOS
Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

.Net
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

horizontal partitioning

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Interbase Change Views

yes

none

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

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

Multiversion concurreny control

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

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.