DBMS > Drizzle vs. GeoMesa vs. Ingres vs. Redis vs. TimescaleDB

System Properties Comparison Drizzle vs. GeoMesa vs. Ingres vs. Redis vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Well established RDBMS

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 time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

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

Time Series DBMS

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

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

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

www.geomesa.org

www.actian.com/databases/ingres

redis.com
redis.io

www.timescale.com

Technical documentation

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

docs.actian.com/ingres

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

docs.timescale.com

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Actian Corporation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Timescale

Initial release

2008

2014

1974

originally developed at University Berkely in early 1970s

2009

2017

Current release

7.2.4, September 2012

4.0.5, February 2024

11.2, May 2022

7.2.4, January 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

commercial

Open Source

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

Open Source

Apache 2.0

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

C++

Scala

Server operating systems

FreeBSD
Linux
OS X

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with RediSQL module

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C
C++
Java
PHP

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
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

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

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

hooks for callbacks inside the server can be used.

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

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

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

Ingres Replicator

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication with hot standby and reads on replicas

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

fine grained access rights according to SQL-standard

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.