DBMS > Amazon Redshift vs. GeoSpock vs. LokiJS vs. Microsoft Azure Cosmos DB

System Properties Comparison Amazon Redshift vs. GeoSpock vs. LokiJS vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Large scale data warehouse service for use with business intelligence tools

Spatial and temporal data processing engine for extreme data scale

In-memory JavaScript DBMS

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

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

Website

aws.amazon.com/redshift

geospock.com

github.com/techfort/LokiJS

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.aws.amazon.com/redshift

techfort.github.io/LokiJS

learn.microsoft.com/azure/cosmos-db

Developer

Amazon (based on PostgreSQL)

GeoSpock

Microsoft

Initial release

2012

2014

Current release

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

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

Java, Javascript

JavaScript

Server operating systems

hosted

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

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

temporal, categorical

yes

via views

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC

JavaScript API

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

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript

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

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

atomic operations within a single collection possible

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

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.