DBMS > BigchainDB vs. Dgraph vs. RavenDB vs. SiteWhere vs. Snowflake

System Properties Comparison BigchainDB vs. Dgraph vs. RavenDB vs. SiteWhere vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Distributed and scalable native Graph DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

M2M integration platform for persisting/querying time series data

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.bigchaindb.com

dgraph.io

ravendb.net

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

dgraph.io/docs

ravendb.net/docs

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Dgraph Labs, Inc.

Hibernating Rhinos

SiteWhere

Snowflake Computing Inc.

Initial release

2016

2010

2014

Current release

5.4, July 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

Open Source

Common Public Attribution License Version 1.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

Python

Java

Server operating systems

Linux

Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

hosted

Data scheme

schema-free

predefined scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (RQL)

yes

APIs and other access methods

CLI Client
RESTful HTTP API

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Synchronous replication via Raft

Multi-source replication

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

User concepts

Access control

yes

Planned for future releases

Authorization levels configured per client per database

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

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.