DBMS > BigchainDB vs. EJDB vs. Hive vs. Memcached vs. Snowflake

System Properties Comparison BigchainDB vs. EJDB vs. Hive vs. Memcached vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

data warehouse software for querying and managing large distributed datasets, built on Hadoop

In-memory key-value store, originally intended for caching

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.27
Rank	#297	Overall
	#44	Document stores

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.bigchaindb.com

github.com/Softmotions/ejdb

hive.apache.org

www.memcached.org

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

github.com/Softmotions/ejdb/blob/master/README.md

cwiki.apache.org/confluence/display/Hive/Home

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Softmotions

Apache Software Foundation

initially developed by Facebook

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Initial release

2016

2012

2003

2014

Current release

3.1.3, April 2022

1.6.25, March 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

GPLv2

Open Source

Apache Version 2

Open Source

BSD license

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

Linux

server-less

All OS with a Java VM

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

string, integer, double, bool, date, object_id

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 DML and DDL statements

yes

APIs and other access methods

CLI Client
RESTful HTTP API

in-process shared library

JDBC
ODBC
Thrift

Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C++
Java
PHP
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

selectable replication factor

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

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.

User concepts

Access control

yes

Access rights for users, groups and roles

yes

using SASL (Simple Authentication and Security Layer) protocol

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.