DBMS > GeoSpock vs. IBM Db2 warehouse vs. JSqlDb vs. Linter vs. Microsoft Azure Cosmos DB

System Properties Comparison GeoSpock vs. IBM Db2 warehouse vs. JSqlDb vs. Linter vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

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

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Cloud-based data warehousing service

JavaScript Query Language Database, stores JavaScript objects and primitives

RDBMS for high security requirements

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

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	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

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

Website

geospock.com

www.ibm.com/products/db2/warehouse

jsqldb.org (offline)

linter.ru

azure.microsoft.com/services/cosmos-db

Technical documentation

learn.microsoft.com/azure/cosmos-db

Developer

GeoSpock

IBM

Konrad von Backstrom

relex.ru

Microsoft

Initial release

2014

2018

1990

2014

Current release

2.0, September 2019

0.8, December 2018

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

C and C++

Server operating systems

hosted

Linux
macOS
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

Data scheme

yes

schema-free

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.

Import/export of XML data possible

Secondary indexes

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

APIs and other access methods

JDBC

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

Supported programming languages

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

JavaScript

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

Server-side scripts

Stored procedures

PL/SQL, SQL PL

functions in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

yes

Implicit feature of the cloud service

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

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

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

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

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.