DBMS > BigchainDB vs. Geode vs. Ignite vs. Snowflake vs. TimesTen

System Properties Comparison BigchainDB vs. Geode vs. Ignite vs. Snowflake vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

In-Memory RDBMS compatible to Oracle

Primary database model

Document store

Key-value store

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	1.86
Rank	#134	Overall
	#24	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	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

geode.apache.org/docs

apacheignite.readme.io/docs

docs.snowflake.net/manuals/index.html

docs.oracle.com/database/timesten-18.1

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Apache Software Foundation

Snowflake Computing Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2016

2002

2015

2014

1998

Current release

1.1, February 2017

Apache Ignite 2.6

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.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

C++, Java, .Net

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

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

SQL-like query language (OQL)

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

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

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

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

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

user defined functions

PL/SQL

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes (replicated cache)

yes

Multi-source replication
Source-replica replication

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

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

by means of logfiles and checkpoints

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

Access rights per client and object definable

Security Hooks for custom implementations

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

fine grained access rights according to SQL-standard

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.