DBMS > BigchainDB vs. Elasticsearch vs. Linter vs. SQLite

System Properties Comparison BigchainDB vs. Elasticsearch vs. Linter vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

RDBMS for high security requirements

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Spatial 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	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.bigchaindb.com

www.elastic.co/elasticsearch

linter.ru

www.sqlite.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

www.sqlite.org/docs.html

Developer

Elastic

relex.ru

Dwayne Richard Hipp

Initial release

2016

2010

1990

2000

Current release

8.6, January 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Elastic License

commercial

Open Source

Public Domain

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

C and C++

Server operating systems

Linux

All OS with a Java VM

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

server-less

Data scheme

schema-free

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

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

by using the 'percolation' feature

yes

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

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

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

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

via file-system locks

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

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.