DBMS > GeoMesa vs. H2 vs. MaxDB vs. Redis vs. SWC-DB

System Properties Comparison GeoMesa vs. H2 vs. MaxDB vs. Redis vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

A robust and reliable RDBMS optimized to run all major SAP solutions

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 high performance, scalable Wide Column DBMS

Primary database model

Spatial DBMS

Relational DBMS

Key-value store

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

Wide column store

Secondary database models

Spatial DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

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

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

www.h2database.com/html/main.html

maxdb.sap.com/documentation

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

Developer

CCRi and others

Thomas Mueller

SAP, acquired from Software AG (Adabas-D) in 1997

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Alex Kashirin

Initial release

2014

2005

1984

2009

2020

Current release

4.0.5, February 2024

2.2.220, July 2023

7.9.10.12, February 2024

7.2.4, January 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

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

commercial

Limited community edition free

Open Source

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

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

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

Scala

Java

C++

Server operating systems

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

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.

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes

with RediSQL module

SQL-like query language

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

proprietary protocol

RESP - REdis Serialization Protocol

Proprietary protocol
Thrift

Supported programming languages

Java

.Net
C#
Java
Perl
PHP
Python

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

C++

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

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

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

Source-replica replication

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

depending on storage layer

Immediate Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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.