DBMS > BigchainDB vs. Graph Engine vs. Ignite vs. Snowflake vs. TinkerGraph

System Properties Comparison BigchainDB vs. Graph Engine vs. Ignite vs. Snowflake vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

Graph DBMS
Key-value store

Key-value store
Relational DBMS

Relational DBMS

Graph DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.graphengine.io/docs/manual

apacheignite.readme.io/docs

docs.snowflake.net/manuals/index.html

Developer

Microsoft

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2016

2010

2015

2014

2009

Current release

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

MIT License

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

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

.NET and C

C++, Java, .Net

Java

Server operating systems

Linux

.NET

Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

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

schema-free

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

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

CLI Client
JDBC
ODBC

TinkerPop 3

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C#
C++
F#
Visual Basic

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Groovy
Java

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes (replicated cache)

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

optional

In-memory capabilities

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

yes

User concepts

Access control

yes

Security Hooks for custom implementations

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.