DBMS > Ehcache vs. FatDB vs. Firebase Realtime Database vs. OpenSearch

System Properties Comparison Ehcache vs. FatDB vs. Firebase Realtime Database vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A widely adopted Java cache with tiered storage options

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Key-value store

Document store
Key-value store

Document store

Search engine

Secondary database models

Vector DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

www.ehcache.org

firebase.google.com/products/realtime-database

github.com/opensearch-project
opensearch.org

Technical documentation

www.ehcache.org/documentation

firebase.google.com/docs/database

opensearch.org/docs/latest

Developer

Terracotta Inc, owned by Software AG

FatCloud

Google

acquired by Google 2014

Amazon Web Services

Initial release

2009

2012

2021

Current release

3.10.0, March 2022

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache Version 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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

Server operating systems

All OS with a Java VM

Windows

hosted

All OS with a Java VM

Data scheme

schema-free

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

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

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

JCache

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Android
iOS
JavaScript API
RESTful HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

Java

Java
JavaScript
Objective-C

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

yes

via applications

limited functionality with using 'rules'

yes

Triggers

yes

Cache Event Listeners

yes

via applications

Callbacks are triggered when data changes

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

Transaction concepts

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

yes

supports JTA and can work as an XA resource

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

User concepts

Access control

Can implement custom security layer via applications

yes, based on authentication and database rules

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.