DBMS > Dgraph vs. IBM Cloudant vs. Snowflake vs. VoltDB

System Properties Comparison Dgraph vs. IBM Cloudant vs. Snowflake vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Database as a Service offering based on Apache CouchDB

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Graph DBMS

Document store

Relational DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

dgraph.io

www.ibm.com/products/cloudant

www.snowflake.com

www.voltdb.com

Technical documentation

dgraph.io/docs

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Dgraph Labs, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2016

2010

2014

2010

Current release

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Erlang

Java, C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X

for development

Data scheme

schema-free

yes

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

yes

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

yes

only a subset of SQL 99

APIs and other access methods

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

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

user defined functions

Java

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

Planned for future releases

Access rights for users can be defined per database

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

Users and roles with access to stored procedures

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.