DBMS > BigchainDB vs. Greenplum vs. Memcached vs. Qdrant vs. Snowflake

System Properties Comparison BigchainDB vs. Greenplum vs. Memcached vs. Qdrant vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

A high-performance vector database with neural network or semantic-based matching

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

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

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.bigchaindb.com

greenplum.org

www.memcached.org

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.greenplum.org

github.com/memcached/memcached/wiki

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

Developer

Pivotal Software Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Qdrant

Snowflake Computing Inc.

Initial release

2016

2005

2003

2021

2014

Current release

7.0.0, September 2023

1.6.27, May 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0

Open Source

BSD license

Open Source

Apache Version 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

Rust

Server operating systems

Linux

FreeBSD
Linux
OS X
Unix
Windows

Docker
Linux
macOS
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

Numbers, Strings, Geo, Boolean

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

since Version 4.2

yes

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC

Proprietary protocol

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
Java
Perl
Python
R

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable 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

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.

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

Key-based authentication

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.