DBMS > BigchainDB vs. Google Cloud Datastore vs. Memcached vs. Snowflake vs. SQream DB

System Properties Comparison BigchainDB vs. Google Cloud Datastore vs. Memcached vs. Snowflake vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Document store

Key-value store

Relational DBMS

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

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

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

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.62
Rank	#234	Overall
	#109	Relational DBMS

Website

www.bigchaindb.com

cloud.google.com/datastore

www.memcached.org

www.snowflake.com

sqream.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

SQream Technologies

Initial release

2016

2008

2003

2014

2017

Current release

1.6.29, June 2024

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

AGPL v3

commercial

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux

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, details here

yes

yes, ANSI Standard SQL Types

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 query language (GQL)

yes

APIs and other access methods

CLI Client
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Proprietary protocol

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

user defined functions in Python

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

none

Repcached, a Memcached patch, provides this functionallity

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

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 based on Google Cloud Identity and Access Management (IAM)

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.