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

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

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.

Edge Time Series DBMS with Real-Time Stream Processing

Distributed, fault tolerant key-value store

Primary database model

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

Secondary database models

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	0.39
Rank	#273	Overall
	#24	Time Series DBMS

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

Website

www.bigchaindb.com

www.geomesa.org

www.ittia.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

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

Developer

CCRi and others

ITTIA L.L.C.

OpenSource, formerly Basho Technologies

Initial release

2016

2014

2007

2009

Current release

4.0.5, February 2024

8.7

3.2.0, December 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache License 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

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

C and C++

Erlang

Server operating systems

Linux

Linux
Windows

Linux
OS X

Data scheme

schema-free

yes

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

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

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API
WebSocket

HTTP API
Native Erlang Interface

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C++
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

Erlang

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"

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

yes

selectable replication factor

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

yes

links between data sets can be stored

Transaction concepts

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

yes

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Database file passwords

yes, using Riak Security

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

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

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

ascribe announces scalable blockchain database BigchainDB - CoinReport
13 February 2016, CoinReport

7 blockchain firms join Bosch led GAIA-X consortium for vehicle identity
13 September 2022, Ledger Insights

provided by Google News

Embedded secured data base for STM32 MCUs
16 October 2023, Electronics Weekly

ITTIA Embedded Time Series Database to Support STM32 Edge Devices
8 April 2022, Embedded Computing Design

Free Healthcare Data for Use with Maptitude 2019 Mapping Software
20 September 2019, GISuser.com

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

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

Share this page