DBMS > GeoMesa vs. OpenQM vs. Riak TS vs. SAP SQL Anywhere

System Properties Comparison GeoMesa vs. OpenQM vs. Riak TS 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.

QpenQM is a high-performance, self-tuning, multi-value DBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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	#214	Overall
	#4	Spatial DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Website

www.geomesa.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

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

Technical documentation

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

www.tiot.jp/riak-docs/riak/ts/latest

help.sap.com/docs/SAP_SQL_Anywhere

Developer

CCRi and others

Rocket Software, originally Martin Phillips

Open Source, formerly Basho Technologies

SAP

formerly Sybase

Initial release

2014

1993

2015

1992

Current release

5.0.1, July 2024

3.4-12

3.0.0, September 2022

17, July 2015

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPLv2, extended commercial license available

Open Source

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

Erlang

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

with some exceptions

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

restricted

yes

SQL

Support of SQL

yes, limited

yes

APIs and other access methods

HTTP API
Native Erlang Interface

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

Server-side scripts

Stored procedures

yes

Erlang

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

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

selectable replication factor

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

Access rights can be defined down to the item level

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

SAP Products & Services Data Portfolio
2 July 2021, Datamation

Securing SAP with AWS Network Firewall: Part 2 – Managed Rules
17 July 2023, AWS Blog

SAP vulnerabilities Let Attacker Inject OS Commands—Patch Now!
11 July 2023, CybersecurityNews

MindsDB is now the leading and fastest growing applied ML platform in the world
3 November 2022, PR Newswire

Gartner’s Magic Quadrant for Cloud Database Management Systems
9 December 2020, CRN

provided by Google News

Share this page