DBMS > Apache Drill vs. Atos Standard Common Repository vs. BigchainDB vs. Memcached vs. Snowflake

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. BigchainDB vs. Memcached vs. Snowflake

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

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

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

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Document store

Key-value store

Relational DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

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

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.bigchaindb.com

www.memcached.org

www.snowflake.com

Technical documentation

drill.apache.org/docs

bigchaindb.readthedocs.io/en/latest

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Initial release

2012

2016

2003

2014

Current release

1.20.3, January 2023

1703

1.6.25, March 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

AGPL v3

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

Java

Python

Server operating systems

Linux
OS X
Windows

Linux

FreeBSD
Linux
OS X
Unix
Windows

hosted

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

optional

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 SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

CLI Client
RESTful HTTP API

Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

C++

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

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.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

LDAP bind authentication

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.