DBMS > BigchainDB vs. Infobright vs. Newts vs. PouchDB vs. Snowflake

System Properties Comparison BigchainDB vs. Infobright vs. Newts vs. PouchDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Time Series DBMS based on Cassandra

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.bigchaindb.com

ignitetech.com/softwarelibrary/infobrightdb

opennms.github.io/newts

pouchdb.com

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

github.com/OpenNMS/newts/wiki

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenNMS Group

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2016

2005

2014

2012

2014

Current release

7.1.1, June 2019

License

Commercial or Open Source

Open Source

AGPL v3

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache 2.0

Open Source

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

JavaScript

Server operating systems

Linux

Linux
Windows

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Data scheme

schema-free

yes

schema-free

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

Knowledge Grid Technology used instead

yes

via views

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP REST
Java API

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

selectable replication factor

based on Cassandra

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

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

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

yes

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.