DBMS > BigchainDB vs. CouchDB vs. GeoMesa vs. LMDB vs. Snowflake

System Properties Comparison BigchainDB vs. CouchDB vs. GeoMesa vs. LMDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A high performant, light-weight, embedded key-value database library

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

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	2.33
Rank	#118	Overall
	#21	Key-value stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

www.bigchaindb.com

couchdb.apache.org

www.geomesa.org

www.symas.com/symas-embedded-database-lmdb

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.couchdb.org/en/stable

www.geomesa.org/documentation/stable/user/index.html

www.lmdb.tech/doc

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

CCRi and others

Symas

Snowflake Computing Inc.

Initial release

2016

2005

2014

2011

2014

Current release

3.3.3, December 2023

4.0.5, February 2024

0.9.32, January 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache version 2

Open Source

Apache License 2.0

Open Source

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

Erlang

Scala

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

Linux
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

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

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

depending on storage layer

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic 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.

depending on storage layer

yes

User concepts

Access control

yes

Access rights for users can be defined per database

yes

depending on the DBMS used for storage

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.