DBMS > BigchainDB vs. Elasticsearch vs. EXASOL vs. FatDB vs. Google BigQuery

System Properties Comparison BigchainDB vs. Elasticsearch vs. EXASOL vs. FatDB vs. Google BigQuery

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

Primary database model

Document store

Search engine

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

www.bigchaindb.com

www.elastic.co/elasticsearch

www.exasol.com

cloud.google.com/bigquery

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.exasol.com/resources

cloud.google.com/bigquery/docs

Developer

Elastic

Exasol

FatCloud

Google

Initial release

2016

2010

2000

2012

2010

Current release

8.6, January 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Elastic License

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

Java

Server operating systems

Linux

All OS with a Java VM

Windows

hosted

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

Via inetgration in SQL Server

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Java API
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

via applications

user defined functions

in JavaScript

Triggers

yes

by using the 'percolation' feature

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying 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.

Memcached and Redis integration

yes

User concepts

Access control

yes

Access rights for users, groups and roles according to SQL-standard

Can implement custom security layer via applications

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.