DBMS > BigchainDB vs. Dolt vs. DuckDB vs. GeoMesa vs. Snowflake

System Properties Comparison BigchainDB vs. Dolt vs. DuckDB vs. GeoMesa vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

A MySQL compatible DBMS with Git-like versioning of data and schema

An embeddable, in-process, column-oriented SQL OLAP RDBMS

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

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

Primary database model

Secondary database models

Document store

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

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	5.61
Rank	#60	Overall
	#34	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.bigchaindb.com

github.com/dolthub/dolt
www.dolthub.com

duckdb.org

www.geomesa.org

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.dolthub.com

duckdb.org/docs

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

docs.snowflake.net/manuals/index.html

Developer

DoltHub Inc

CCRi and others

Snowflake Computing Inc.

Initial release

2016

2018

2014

Current release

1.0.0, June 2024

5.0.1, July 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2.0

Open Source

MIT License

Open Source

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

C++

Scala

Server operating systems

Linux

Linux
macOS
Windows

server-less

hosted

Data scheme

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

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

CLI Client
HTTP REST

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

none

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

depending on storage layer

User concepts

Access control

yes

Only one user is configurable, and must be specified in the config file at startup

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.