DBMS > BigchainDB vs. Elasticsearch vs. Snowflake vs. Typesense

System Properties Comparison BigchainDB vs. Elasticsearch vs. Snowflake vs. Typesense

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

Cloud-based data warehousing service for structured and semi-structured data

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

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	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.79
Rank	#210	Overall
	#14	Search engines

Website

www.bigchaindb.com

www.elastic.co/elasticsearch

www.snowflake.com

typesense.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

docs.snowflake.net/manuals/index.html

typesense.org/docs

Developer

Elastic

Snowflake Computing Inc.

Initial release

2016

2010

2014

2015

Current release

8.6, January 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Elastic License

commercial

Open Source

GPL V3

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

C++

Server operating systems

Linux

All OS with a Java VM

hosted

Linux

Data scheme

schema-free

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

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

pre-defined schema optional

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

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

JavaScript (Node.js)
Python

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication using RAFT

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.