DBMS > Amazon Redshift vs. GeoMesa vs. OpenQM vs. VelocityDB

System Properties Comparison Amazon Redshift vs. GeoMesa vs. OpenQM vs. VelocityDB

Please select another system to include it in the comparison.

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.

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Relational DBMS

Spatial DBMS

Multivalue DBMS

Graph DBMS
Object oriented DBMS

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	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#16	Object oriented DBMS

Website

aws.amazon.com/redshift

www.geomesa.org

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

velocitydb.com

Technical documentation

docs.aws.amazon.com/redshift

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

velocitydb.com/UserGuide

Developer

Amazon (based on PostgreSQL)

CCRi and others

Rocket Software, originally Martin Phillips

VelocityDB Inc

Initial release

2012

2014

1993

2011

Current release

5.0.0, May 2024

3.4-12

7.x

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

GPLv2, extended commercial license available

commercial

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

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Any that supports .NET

Data scheme

yes

with some exceptions

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

.Net

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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.

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

Access rights can be defined down to the item level

Based on Windows Authentication

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.