DBMS > GeoMesa vs. Ingres vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison GeoMesa vs. Ingres vs. RocksDB vs. SAP SQL Anywhere

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.

Well established RDBMS

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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.11
Rank	#81	Overall
	#44	Relational DBMS

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

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.geomesa.org

www.actian.com/databases/ingres

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

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

docs.actian.com/ingres

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

CCRi and others

Actian Corporation

Facebook, Inc.

SAP

formerly Sybase

Initial release

2014

1974

originally developed at University Berkely in early 1970s

2013

1992

Current release

5.0.0, May 2024

11.2, May 2022

9.2.1, May 2024

17, July 2015

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

Server operating systems

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Ingres Replicator

yes

Source-replica replication

Database mirroring

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

MVCC

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.