DBMS > BoltDB vs. Microsoft Azure Cosmos DB vs. NSDb vs. Postgres-XL vs. TigerGraph

System Properties Comparison BoltDB vs. Microsoft Azure Cosmos DB vs. NSDb vs. Postgres-XL vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Globally distributed, horizontally scalable, multi-model database service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

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

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

github.com/boltdb/bolt

azure.microsoft.com/services/cosmos-db

nsdb.io

www.postgres-xl.org

www.tigergraph.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

www.postgres-xl.org/documentation

docs.tigergraph.com

Developer

Microsoft

Initial release

2013

2014

2017

2014

since 2012, originally named StormDB

2017

Current release

10 R1, October 2018

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache Version 2.0

Open Source

Mozilla public license

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, Scala

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux
macOS

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes: int, bigint, decimal, string

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

XML type, but no XML query functionality

Secondary indexes

yes

All properties auto-indexed by default

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

SQL-like query language (GSQL)

APIs and other access methods

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

gRPC
HTTP REST
WebSocket

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

Java
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C++
Java

Server-side scripts

Stored procedures

JavaScript

user defined functions

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

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*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

In-memory capabilities

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

User concepts

Access control

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Role-based access control

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.