DBMS > BigchainDB vs. KeyDB vs. Machbase Neo vs. SpaceTime vs. Yaacomo

System Properties Comparison BigchainDB vs. KeyDB vs. Machbase Neo vs. SpaceTime vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

TimeSeries DBMS for AIoT and BigData

SpaceTime is a spatio-temporal DBMS with a focus on performance.

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Secondary database models

Relational DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

www.bigchaindb.com

github.com/Snapchat/KeyDB
keydb.dev

machbase.com

www.mireo.com/spacetime

yaacomo.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.keydb.dev

machbase.com/dbms

Developer

EQ Alpha Technology Ltd.

Machbase

Mireo

Q2WEB GmbH

Initial release

2016

2019

2013

2020

2009

Current release

V8.0, August 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

BSD-3

commercial

free test version available

commercial

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

C++

Server operating systems

Linux

Linux
macOS
Windows

Linux

Android
Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like query language

A subset of ANSI SQL is implemented

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

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

RESTful HTTP API

JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C#
C++
Python

Server-side scripts

Stored procedures

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Fixed-grid hypercubes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

selectable replication factor

Real-time block device replication (DRBD)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

yes

User concepts

Access control

yes

simple password-based access control and ACL

simple password-based access control

yes

fine grained access rights according to SQL-standard

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

Recent citations in the news

BigchainDB • • The blockchain database.
4 February 2016, bigchaindb.com

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 - Ledger Insights
13 September 2022, Ledger Insights

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Share this page