DBMS > AgensGraph vs. Apache Druid vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage

System Properties Comparison AgensGraph vs. Apache Druid vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS
Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Secondary database models

Spatial DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Website

bitnine.net/agensgraph

druid.apache.org

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

bitnine.net/documentation

druid.apache.org/docs/latest/design

learn.microsoft.com/azure/cosmos-db

Developer

Bitnine Global Inc.

Apache Software Foundation and contributors

Microsoft

Initial release

2016

2012

2014

2012

Current release

2.1, December 2018

29.0.1, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache license v2

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

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix

hosted

Data scheme

depending on used data model

yes

schema-less columns are supported

schema-free

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL for querying

SQL-like query language

APIs and other access methods

Cypher Query Language
JDBC

JDBC
RESTful HTTP/JSON API

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

RESTful HTTP API

Supported programming languages

C
Java
JavaScript
Python

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

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

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

Sharding

manual/auto, time-based

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, via HDFS, S3 or other storage engines

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

optimistic locking

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.