DBMS > BoltDB vs. Elasticsearch vs. EXASOL vs. Infobright vs. Snowflake

System Properties Comparison BoltDB vs. Elasticsearch vs. EXASOL vs. Infobright vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Primary database model

Key-value store

Search engine

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.80
Rank	#215	Overall
	#31	Key-value stores

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/boltdb/bolt

www.elastic.co/elasticsearch

www.exasol.com

ignitetech.com/softwarelibrary/infobrightdb

www.snowflake.com

Technical documentation

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

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

Developer

Elastic

Exasol

Ignite Technologies Inc.; formerly InfoBright Inc.

Snowflake Computing Inc.

Initial release

2013

2010

2000

2005

2014

Current release

8.6, January 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Elastic License

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
Windows

hosted

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)

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

Knowledge Grid Technology used instead

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.