DBMS > Elasticsearch vs. LevelDB vs. Snowflake vs. VoltDB

System Properties Comparison Elasticsearch vs. LevelDB vs. Snowflake vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Search engine

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	128.79
Rank	#8	Overall
	#1	Search engines

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

www.elastic.co/elasticsearch

github.com/google/leveldb

www.snowflake.com

www.voltdb.com

Technical documentation

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

github.com/google/leveldb/blob/main/doc/index.md

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Elastic

Google

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2010

2011

2014

2010

Current release

8.6, January 2023

1.23, February 2021

11.3, April 2022

License

Commercial or Open Source

Open Source

Elastic License

Open Source

BSD

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Server operating systems

All OS with a Java VM

Illumos
Linux
OS X
Windows

hosted

Linux
OS X

for development

Data scheme

schema-free

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

schema-free

yes

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

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.

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

Java

Triggers

yes

by using the 'percolation' feature

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Memcached and Redis integration

User concepts

Access control

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

Users and roles with access to stored procedures

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.