DBMS > EXASOL vs. GeoMesa vs. OpenQM vs. RavenDB vs. SwayDB

System Properties Comparison EXASOL vs. GeoMesa vs. OpenQM vs. RavenDB vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

www.exasol.com

www.geomesa.org

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

ravendb.net

swaydb.simer.au

Technical documentation

www.exasol.com/resources

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

ravendb.net/docs

Developer

Exasol

CCRi and others

Rocket Software, originally Martin Phillips

Hibernating Rhinos

Simer Plaha

Initial release

2000

2014

1993

2010

2018

Current release

5.0.0, May 2024

3.4-12

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

GPLv2, extended commercial license available

Open Source

AGPL version 3, commercial license available

Open Source

GNU Affero GPL V3.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

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

with some exceptions

schema-free

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

SQL

Support of SQL

yes

SQL-like query language (RQL)

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

Java
Lua
Python
R

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Atomic execution of operations

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.

yes

depending on storage layer

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

Authorization levels configured per client per database

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

It's Back to the Database Future for Exasol CEO Tewes
26 October 2023, Datanami

Exasol Finds AI Underinvestment Leads to Business Failure, But Data Challenges Stall Rapid Adoption
20 March 2024, Business Wire

Exasol gets jolt of AI with Espresso suite of capabilities
26 February 2024, TechTarget

Mathias Golombek, Chief Technology Officer of Exasol – Interview Series
21 May 2024, Unite.AI

Exasol Unveils New Suite of AI Tools to Turbocharge Enterprise Data Analytics
22 February 2024, AiThority

provided by Google News

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

RavenDB Adds Graph Queries
15 May 2019, Datanami

Review: NoSQL database RavenDB
20 March 2019, TechGenix

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

Share this page