DBMS > BigchainDB vs. PouchDB vs. Snowflake vs. Splice Machine vs. Valentina Server

System Properties Comparison BigchainDB vs. PouchDB vs. Snowflake vs. Splice Machine vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

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

JavaScript DBMS with an API inspired by CouchDB

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Object-relational database and reports server

Primary database model

Document store

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

splicemachine.com/how-it-works

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Apache Software Foundation

Snowflake Computing Inc.

Splice Machine

Paradigma Software

Initial release

2016

2012

2014

1999

Current release

7.1.1, June 2019

3.1, March 2021

5.7.5

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

commercial

Open Source

AGPL 3.0, commercial license available

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

JavaScript

Java

Server operating systems

Linux

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

hosted

Linux
OS X
Solaris
Windows

Linux
OS X
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

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

JavaScript

JavaScript (Node.js)
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

yes

Java

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes, multi-version concurrency control (MVCC)

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

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

Access rights for users, groups and roles according to SQL-standard

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.