DBMS > Firebase Realtime Database vs. NCache vs. Redis vs. Solr vs. SQL.JS

System Properties Comparison Firebase Realtime Database vs. NCache vs. Redis vs. Solr vs. SQL.JS

Editorial information provided by DB-Engines

Name

Description

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

Open-Source and Enterprise in-memory Key-Value Store

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

A widely used distributed, scalable search engine based on Apache Lucene

Port of SQLite to JavaScript

Primary database model

Document store

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Search engine

Relational DBMS

Secondary database models

Document store
Search engine

Using distributed Lucene

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Spatial DBMS

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.96
Rank	#195	Overall
	#29	Key-value stores

Score	155.94
Rank	#6	Overall
	#1	Key-value stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.alachisoft.com/ncache

redis.com
redis.io

solr.apache.org

sql.js.org

Technical documentation

firebase.google.com/docs/database

www.alachisoft.com/resources/docs

docs.redis.com/latest/index.html
redis.io/docs

solr.apache.org/resources.html

sql.js.org/documentation/index.html

Developer

Google

acquired by Google 2014

Alachisoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Apache Software Foundation

Alon Zakai

enhancements implemented by others

Initial release

2012

2005

2009

2006

2012

Current release

5.3.3, April 2024

7.2.5, May 2024

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Enterprise Edition available

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

Open Source

Apache Version 2

Open Source

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 Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

C#, .NET, .NET Core, Java

Java

JavaScript

Server operating systems

hosted

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are Lists, Queues, Hashsets, Dictionary and Counter

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

supports customizable data types and automatic typing

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

with RediSearch module

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query syntax and LINQ for searching the cache. Cache Synchronization with SQL Server using SQL dependency.

with RediSQL module

Solr Parallel SQL Interface

yes

SQL-92 is not fully supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

IDistributedCache
JCache
LINQ
Proprietary native API

proprietary protocol

RESP - REdis Serialization Protocol

Java API
RESTful HTTP/JSON API

JavaScript API

Supported programming languages

Java
JavaScript
Objective-C

.Net
.Net Core
C#
Java
JavaScript (Node.js)
Python
Scala

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

limited functionality with using 'rules'

support for stored procedures with SQL-Server CLR

Lua; Redis Functions coming in Redis 7 (slides and Github)

Java plugins

Triggers

Callbacks are triggered when data changes

yes

Notifications

publish/subscribe channels provide some trigger functionality; RedisGears

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with selectable consistency level

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency
Immediate Consistency
Strong Eventual Consistency over WAN with Conflict Resolution using Bridge Topology

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Eventual Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

optimistic locking and pessimistic locking

Atomic execution of command blocks and scripts and optimistic locking

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

except by serializing a db to a file

In-memory capabilities

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

yes

User concepts

Access control

yes, based on authentication and database rules

Authentication to access the cache via Active Directory/LDAP (possible roles: user, administrator)

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

yes

More information provided by the system vendor

Specific characteristics

NCache has been the market leader in .NET Distributed Caching since 2005 . NCache...
» more

Competitive advantages

NCache is 100% .NET/ .NET Core based which fully supports ASP.NET Core Sessions ,...
» more

Typical application scenarios

NCache enables industries like retail, finance, banking IoT, travel, ecommerce, healthcare...
» more

Key customers

Bank of America, Citi, Natures Way, Charter Spectrum, Barclays, Henry Schein, GBM,...
» more

Market metrics

Market Leader in .NET Distributed Caching since 2005.
» more

Licensing and pricing models

NCache Open Source is free on an as-is basis without any support. NCache Enterprise...
» 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.