DBMS > BigchainDB vs. Drizzle vs. GeoMesa vs. Graph Engine vs. Hawkular Metrics

System Properties Comparison BigchainDB vs. Drizzle vs. GeoMesa vs. Graph Engine vs. Hawkular Metrics

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Primary database model

Document store

Relational DBMS

Spatial DBMS

Graph DBMS
Key-value store

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.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

www.graphengine.io/docs/manual

www.hawkular.org/hawkular-metrics/docs/user-guide

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Microsoft

Community supported by Red Hat

Initial release

2016

2008

2014

2010

2014

Current release

7.2.4, September 2012

5.0.0, May 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

GNU GPL

Open Source

Apache License 2.0

Open Source

MIT License

Open Source

Apache 2.0

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++

Scala

.NET and C

Java

Server operating systems

Linux

FreeBSD
Linux
OS X

.NET

Linux
OS X
Windows

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC

RESTful HTTP API

HTTP REST

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C++
Java
PHP

C#
C++
F#
Visual Basic

Go
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

hooks for callbacks inside the server can be used.

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

horizontal partitioning

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

depending on storage layer

selectable replication factor

based on Cassandra

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

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

depending on the DBMS used for storage

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

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

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

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

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

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

provided by Google News

Trinity
30 October 2010, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

provided by Google News

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

Share this page