DBMS > AlaSQL vs. Geode vs. H2 vs. Microsoft Azure SQL Database vs. Redis

System Properties Comparison AlaSQL vs. Geode vs. H2 vs. Microsoft Azure SQL Database vs. Redis

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Database as a Service offering with high compatibility to Microsoft SQL Server

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

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

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

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

Website

alasql.org

geode.apache.org

www.h2database.com

azure.microsoft.com/en-us/products/azure-sql/database

redis.com
redis.io

Technical documentation

github.com/AlaSQL/alasql

geode.apache.org/docs

www.h2database.com/html/main.html

docs.microsoft.com/en-us/azure/azure-sql

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

Developer

Andrey Gershun & Mathias R. Wulff

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Thomas Mueller

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2014

2002

2005

2010

2009

Current release

1.1, February 2017

2.2.220, July 2023

V12

7.2.5, May 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

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

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

JavaScript

Java

C++

Server operating systems

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

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

hosted

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 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

with RediSearch module

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language (OQL)

yes

with RediSQL module

APIs and other access methods

JavaScript API

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

JavaScript

.Net
All JVM based languages
C++
Groovy
Java
Scala

Java

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

user defined functions

Java Stored Procedures and User-Defined Functions

Transact SQL

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

Triggers

yes

Cache Event Listeners

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

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

yes, with always 3 replicas available

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

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

only for local storage and DOM-storage

yes, on a single node

ACID

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

by using IndexedDB, SQL.JS or proprietary FileStorage

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 per client and object definable

fine grained access rights according to SQL-standard

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.