DBMS > BigchainDB vs. Hazelcast vs. Heroic vs. Lovefield vs. Machbase Neo

System Properties Comparison BigchainDB vs. Hazelcast vs. Heroic vs. Lovefield vs. Machbase Neo

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted in-memory data grid

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable relational database for web apps written in pure JavaScript

TimeSeries DBMS for AIoT and BigData

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Website

www.bigchaindb.com

hazelcast.com

github.com/spotify/heroic

google.github.io/lovefield

machbase.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

hazelcast.org/imdg/docs

spotify.github.io/heroic

github.com/google/lovefield/blob/master/docs/spec_index.md

machbase.com/dbms

Developer

Hazelcast

Spotify

Google

Machbase

Initial release

2016

2008

2014

2013

Current release

5.3.6, November 2023

2.1.12, February 2017

V8.0, August 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

free test version available

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

Java

JavaScript

Server operating systems

Linux

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
macOS
Windows

Data scheme

schema-free

yes

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

the object must implement a serialization strategy

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

JavaScript

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Triggers

yes

Events

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Replicated Map

yes

none

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

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

yes

using MemoryDB

yes

volatile and lookup table

User concepts

Access control

yes

Role-based access control

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

Recent citations in the news

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

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

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

Hazelcast Showcases Real-Time Data Platform at 2024 Gartner Summit
15 May 2024, Datanami

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast Versus Redis: A Practical Comparison
4 January 2024, Database Trends and Applications

Hazelcast: The 'true' value of streaming real-time data
27 September 2023, ComputerWeekly.com

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page