DBMS > CrateDB vs. GeoMesa vs. Microsoft Azure AI Search vs. Redis vs. Riak TS

System Properties Comparison CrateDB vs. GeoMesa vs. Microsoft Azure AI Search vs. Redis vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

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

Search-as-a-service for web and mobile app development

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.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Spatial DBMS

Search engine

Key-value store

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

Time Series DBMS

Secondary database models

Relational DBMS

Vector 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.73
Rank	#224	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#8	Vector DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

cratedb.com

www.geomesa.org

azure.microsoft.com/en-us/services/search

redis.com
redis.io

Technical documentation

cratedb.com/docs

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

learn.microsoft.com/en-us/azure/search

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

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Crate

CCRi and others

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Open Source, formerly Basho Technologies

Initial release

2013

2014

2015

2009

2015

Current release

4.0.5, February 2024

7.2.4, January 2024

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

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

Open Source

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.

CrateDB Cloud: a distributed SQL database that spreads data and processing across an elastic cluster of shared nothing nodes. CrateDB Cloud enables data insights at scale on Microsoft Azure, AWS and Google Cloud Platform.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

Scala

Erlang

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X

Data scheme

Flexible Schema (defined schema, partial schema, 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.

Secondary indexes

yes

with RediSearch module

restricted

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

with RediSQL module

yes, limited

APIs and other access methods

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

HTTP API
Native Erlang Interface

Supported programming languages

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

C#
Java
JavaScript
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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions (Javascript)

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

Erlang

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

depending on storage layer

yes

Implicit feature of the cloud service

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Read-after-write consistency on record level

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

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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

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

rights management via user accounts

yes

depending on the DBMS used for storage

yes

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

Specific characteristics

The enterprise database for time series, documents, and vectors. Distributed - Native...
» more

Competitive advantages

Response time in milliseconds: e ven for complex ad-hoc queries. Massive scaling...
» more

Typical application scenarios

IoT: accelerate your IIoT projects with CrateDB, delivering real-time analytics...
» more

Key customers

Across all continents, CrateDB is used by companies of all sizes to meet the most...
» more

Market metrics

The CrateDB open source project was started in 2013 Honorable Mention in 2021 Gartner®...
» more

Licensing and pricing models

See CrateDB pricing >
» 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.