DBMS > Dgraph vs. Google Cloud Datastore vs. IRONdb vs. NSDb vs. RocksDB

System Properties Comparison Dgraph vs. Google Cloud Datastore vs. IRONdb vs. NSDb vs. RocksDB

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed and scalable native Graph DBMS

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

dgraph.io

cloud.google.com/datastore

www.circonus.com/solutions/time-series-database/

nsdb.io

rocksdb.org

Technical documentation

dgraph.io/docs

cloud.google.com/datastore/docs

docs.circonus.com/irondb/category/getting-started

nsdb.io/Architecture

github.com/facebook/rocksdb/wiki

Developer

Dgraph Labs, Inc.

Google

Circonus LLC.

Facebook, Inc.

Initial release

2016

2008

2017

2013

Current release

V0.10.20, January 2018

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

Open Source

BSD

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

C and C++

Java, Scala

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

Linux
macOS

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

text, numeric, histograms

yes: int, bigint, decimal, string

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 fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP API

gRPC
HTTP REST
WebSocket

C++ API
Java API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

yes, in Lua

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Automatic, metric affinity per node

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication using Paxos

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

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.

yes

User concepts

Access control

Planned for future releases

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.