DBMS > Amazon Redshift vs. GeoMesa vs. MonetDB vs. TerminusDB vs. Warp 10

System Properties Comparison Amazon Redshift vs. GeoMesa vs. MonetDB vs. TerminusDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

A relational database management system that stores data in columns

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.72
Rank	#141	Overall
	#64	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

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

www.monetdb.org/Documentation

terminusdb.github.io/terminusdb/#

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

CCRi and others

MonetDB BV

DataChemist Ltd.

SenX

Initial release

2012

2014

2004

2018

2015

Current release

5.0.0, May 2024

Dec2023 (11.49), December 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Mozilla Public License 2.0

Open Source

GPL V3

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Prolog, Rust

Java

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL 2003 with some extensions

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

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

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes, in SQL, C, R

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding via remote tables

Graph Partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

none

Source-replica replication available in experimental status

Journaling Streams

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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 journaling

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Role-based access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.