DBMS > BigchainDB vs. GeoMesa vs. Riak KV vs. Sequoiadb

System Properties Comparison BigchainDB vs. GeoMesa vs. Riak KV vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Distributed, fault tolerant key-value store

NewSQL database with distributed OLTP and SQL

Primary database model

Document store

Spatial DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Document store
Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

www.bigchaindb.com

www.geomesa.org

www.sequoiadb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

www.tiot.jp/riak-docs/riak/kv/latest

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

CCRi and others

OpenSource, formerly Basho Technologies

Sequoiadb Ltd.

Initial release

2016

2014

2009

2013

Current release

4.0.5, February 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

Server: AGPL; Client: Apache V2

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

Scala

Erlang

C++

Server operating systems

Linux

Linux
OS X

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

HTTP API
Native Erlang Interface

proprietary protocol using JSON

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

Erlang

JavaScript

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

Document is locked during a transaction

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.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

yes, using Riak Security

simple password-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Exploring the 10 BEST Python Libraries for Blockchain Applications
9 September 2023, DataDrivenInvestor

An Introduction to BigchainDB, a Popular Blockchain Database
17 September 2020, Open Source For You

Blockchain Database Startup BigchainDB Raises €3 Million
27 September 2016, CoinDesk

Using BigchainDB: A Database with Blockchain Characteristics
20 January 2022, Open Source For You

What is BigchainDB Technology & How it works and the Characteristics?
26 August 2017, Blockchain Council

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page