DBMS > GeoSpock vs. Microsoft Azure Cosmos DB vs. OpenQM vs. SiteWhere vs. SQL.JS

System Properties Comparison GeoSpock vs. Microsoft Azure Cosmos DB vs. OpenQM vs. SiteWhere vs. SQL.JS

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

Globally distributed, horizontally scalable, multi-model database service

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

M2M integration platform for persisting/querying time series data

Port of SQLite to JavaScript

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Multivalue DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

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

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

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

geospock.com

azure.microsoft.com/services/cosmos-db

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

github.com/sitewhere/sitewhere

sql.js.org

Technical documentation

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

sql.js.org/documentation/index.html

Developer

GeoSpock

Microsoft

Rocket Software, originally Martin Phillips

SiteWhere

Alon Zakai

enhancements implemented by others

Initial release

2014

1993

2010

2012

Current release

2.0, September 2019

3.4-12

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

Common Public Attribution License Version 1.0

Open Source

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

Java

JavaScript

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

yes

schema-free

yes

with some exceptions

predefined scheme

yes

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.

yes

Secondary indexes

temporal, categorical

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

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

HTTP REST

JavaScript API

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Implicit feature of the cloud service

yes

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

selectable replication factor

based on HBase

none

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

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users can be defined per table

Access rights can be defined down to the item level

Users with fine-grained authorization concept

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.