DBMS > Amazon DocumentDB vs. BigchainDB vs. Infobright vs. Newts vs. Snowflake

System Properties Comparison Amazon DocumentDB vs. BigchainDB vs. Infobright vs. Newts vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

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	1.91
Rank	#132	Overall
	#24	Document stores

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	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/documentdb

www.bigchaindb.com

ignitetech.com/softwarelibrary/infobrightdb

opennms.github.io/newts

www.snowflake.com

Technical documentation

aws.amazon.com/documentdb/resources

bigchaindb.readthedocs.io/en/latest

github.com/OpenNMS/newts/wiki

docs.snowflake.net/manuals/index.html

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenNMS Group

Snowflake Computing Inc.

Initial release

2019

2016

2005

2014

License

Commercial or Open Source

commercial

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

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

Server operating systems

hosted

Linux

Linux
Windows

Linux
OS X
Windows

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

yes

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP REST
Java API

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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 (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

selectable replication factor

Source-replica replication

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

Access rights for users and roles

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.