DBMS > Elasticsearch vs. Firebase Realtime Database vs. RocksDB vs. Valentina Server vs. Warp 10

System Properties Comparison Elasticsearch vs. Firebase Realtime Database vs. RocksDB vs. Valentina Server vs. Warp 10

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Object-relational database and reports server

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.elastic.co/elasticsearch

firebase.google.com/products/realtime-database

rocksdb.org

www.valentina-db.net

www.warp10.io

Technical documentation

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

firebase.google.com/docs/database

github.com/facebook/rocksdb/wiki

valentina-db.com/docs/dokuwiki/v5/doku.php

www.warp10.io/content/02_Getting_started

Developer

Elastic

Google

acquired by Google 2014

Facebook, Inc.

Paradigma Software

SenX

Initial release

2010

2012

2013

1999

2015

Current release

8.6, January 2023

9.2.1, May 2024

5.7.5

License

Commercial or Open Source

Open Source

Elastic License

commercial

Open Source

BSD

commercial

Open Source

Apache License 2.0

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

Server operating systems

All OS with a Java VM

hosted

Linux

Linux
OS X
Windows

Data scheme

schema-free

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

schema-free

yes

schema-free

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

APIs and other access methods

Java API
RESTful HTTP/JSON API

Android
iOS
JavaScript API
RESTful HTTP API

C++ API
Java API

ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

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

Java
JavaScript
Objective-C

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

yes

WarpScript

Triggers

yes

by using the 'percolation' feature

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.