DBMS > AgensGraph vs. GeoSpock vs. KairosDB vs. Microsoft Azure Cosmos DB

System Properties Comparison AgensGraph vs. GeoSpock vs. KairosDB 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

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Spatial and temporal data processing engine for extreme data scale

Distributed Time Series DBMS based on Cassandra or H2

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Time Series 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	0.17
Rank	#320	Overall
	#29	Graph DBMS
	#143	Relational DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

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

Website

bitnine.net/agensgraph

geospock.com

github.com/kairosdb/kairosdb

azure.microsoft.com/services/cosmos-db

Technical documentation

bitnine.net/documentation

kairosdb.github.io

learn.microsoft.com/azure/cosmos-db

Developer

Bitnine Global Inc.

GeoSpock

Microsoft

Initial release

2016

2013

2014

Current release

2.1, December 2018

2.0, September 2019

1.2.2, November 2018

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

hosted

Data scheme

depending on used data model

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

yes

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

Cypher Query Language
JDBC

JDBC

Graphite protocol
HTTP REST
Telnet API

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

Supported programming languages

C
Java
JavaScript
Python

Java
JavaScript

Node.js
PHP
Python

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

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Automatic sharding

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

simple password-based access control

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.