DBMS > BigchainDB vs. GeoMesa vs. Machbase Neo vs. Riak KV vs. TempoIQ

System Properties Comparison BigchainDB vs. GeoMesa vs. Machbase Neo vs. Riak KV vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

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.

TimeSeries DBMS for AIoT and BigData

Distributed, fault tolerant key-value store

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

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

Time Series DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

www.bigchaindb.com

www.geomesa.org

machbase.com

tempoiq.com (offline)

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

machbase.com/dbms

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

Developer

CCRi and others

Machbase

OpenSource, formerly Basho Technologies

TempoIQ

Initial release

2016

2014

2013

2009

2012

Current release

5.0.0, May 2024

V8.0, August 2023

3.2.0, December 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache License 2.0

commercial

free test version available

Open Source

Apache version 2, commercial enterprise edition

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

Scala

Erlang

Server operating systems

Linux

Linux
macOS
Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

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

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

links between data sets can be stored

Transaction concepts

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

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

yes

volatile and lookup table

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control

yes, using Riak Security

simple authentication-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

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

BigchainDB Raises €3M Series A Funding
28 September 2016, FinSMEs

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

Catena-X Welcomes New Members: Bosch, Ocean Protocol, Fetch.ai
20 May 2021, Coinspeaker

provided by Google News

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

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

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

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

provided by Google News

No-Code Internet of Things Development Platform
29 October 2015, Automation World

provided by Google News

Share this page