DBMS > Google Cloud Firestore vs. H2 vs. LokiJS vs. Microsoft Azure Data Explorer vs. Redis

System Properties Comparison Google Cloud Firestore vs. H2 vs. LokiJS vs. Microsoft Azure Data Explorer vs. Redis

Editorial information provided by DB-Engines

Name

Description

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

In-memory JavaScript DBMS

Fully managed big data interactive analytics platform

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

column oriented

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

Secondary database models

Spatial DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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	7.36
Rank	#53	Overall
	#9	Document stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

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

Website

firebase.google.com/products/firestore

www.h2database.com

github.com/techfort/LokiJS

azure.microsoft.com/services/data-explorer

redis.com
redis.io

Technical documentation

firebase.google.com/docs/firestore

www.h2database.com/html/main.html

techfort.github.io/LokiJS

docs.microsoft.com/en-us/azure/data-explorer

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

Developer

Google

Thomas Mueller

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2017

2005

2014

2019

2009

Current release

2.2.220, July 2023

cloud service with continuous releases

7.2.5, May 2024

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

commercial

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

Java

JavaScript

Server operating systems

hosted

All OS with a Java VM

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

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

schema-free

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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.

yes

Secondary indexes

yes

via views

all fields are automatically indexed

yes

with RediSearch module

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

with RediSQL module

APIs and other access methods

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

JavaScript API

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Java

JavaScript

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

yes, Firebase Rules & Cloud Functions

Java Stored Procedures and User-Defined Functions

View functions in JavaScript

Yes, possible languages: KQL, Python, R

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

Triggers

yes, with Cloud Functions

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

With clustering: 2 database servers on different computers operate on identical copies of a database

none

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Spark connector (open source): github.com/Azure/azure-kusto-spark

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

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

ACID

atomic operations within a single collection possible

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

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

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.