DBMS > GeoSpock vs. Ingres vs. Microsoft Azure Cosmos DB vs. NuoDB vs. OpenQM

System Properties Comparison GeoSpock vs. Ingres vs. Microsoft Azure Cosmos DB vs. NuoDB vs. OpenQM

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Well established RDBMS

Globally distributed, horizontally scalable, multi-model database service

NuoDB is a webscale distributed database that supports SQL and ACID transactions

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

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Multivalue DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Website

geospock.com

www.actian.com/databases/ingres

azure.microsoft.com/services/cosmos-db

www.3ds.com/nuodb-distributed-sql-database

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

Technical documentation

docs.actian.com/ingres

learn.microsoft.com/azure/cosmos-db

doc.nuodb.com

Developer

GeoSpock

Actian Corporation

Microsoft

Dassault Systèmes

originally NuoDB, Inc.

Rocket Software, originally Martin Phillips

Initial release

1974

originally developed at University Berkely in early 1970s

2014

2013

1993

Current release

2.0, September 2019

11.2, May 2022

3.4-12

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPLv2, extended commercial license available

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

Java, Javascript

C++

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

schema-free

yes

with some exceptions

Typing

predefined data types such as float or date

yes

JSON types

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

temporal, categorical

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

yes

APIs and other access methods

JDBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript

Java, SQL

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Implicit feature of the cloud service

data is dynamically stored/cached on the nodes where it is read/written

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes

Implicit feature of the cloud service

yes

Managed transparently by NuoDB

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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.

yes

Temporary table

User concepts

Access control

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Standard SQL roles/ privileges, Administrative Users

Access rights can be defined down to the item level

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.