DBMS > Firebase Realtime Database vs. LokiJS vs. Microsoft Access vs. NCache vs. Redis

System Properties Comparison Firebase Realtime Database vs. LokiJS vs. Microsoft Access vs. NCache vs. Redis

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.

In-memory JavaScript DBMS

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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.

Primary database model

Document store

Relational DBMS

Key-value store

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

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

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

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

Website

firebase.google.com/products/realtime-database

github.com/techfort/LokiJS

www.microsoft.com/en-us/microsoft-365/access

www.alachisoft.com/ncache

redis.com
redis.io

Technical documentation

firebase.google.com/docs/database

techfort.github.io/LokiJS

developer.microsoft.com/en-us/access

www.alachisoft.com/resources/docs

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

Developer

Google

acquired by Google 2014

Microsoft

Alachisoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

2014

1992

2005

2009

Current release

1902 (16.0.11328.20222), March 2019

5.3.3, April 2024

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Bundled with Microsoft Office

Open Source

Enterprise Edition available

Open Source

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

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

JavaScript

C++

C#, .NET, .NET Core, Java

Server operating systems

hosted

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

Windows

Not a real database server, but making use of DLLs

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

yes

schema-free

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

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

via views

yes

with RediSearch module

SQL

Support of SQL

yes

but not compliant to any SQL standard

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

with RediSQL module

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JavaScript API

ADO.NET
DAO
ODBC
OLE DB

IDistributedCache
JCache
LINQ
Proprietary native API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Java
JavaScript
Objective-C

JavaScript

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

support for stored procedures with SQL-Server CLR

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

Triggers

Callbacks are triggered when data changes

yes

since Access 2010 using the ACE-engine

yes

Notifications

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with selectable consistency level

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

atomic operations within a single collection possible

ACID

but no files for transaction logging

optimistic locking and pessimistic locking

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

but no files for transaction logging

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

a simple user-level security was built in till version Access 2003

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

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.