DBMS > Google Cloud Datastore vs. Qdrant vs. Redis vs. Sphinx

System Properties Comparison Google Cloud Datastore vs. Qdrant vs. Redis vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A high-performance vector database with neural network or semantic-based matching

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.

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store

Vector DBMS

Key-value store

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

Search engine

Secondary database models

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	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

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

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

cloud.google.com/datastore

github.com/qdrant/qdrant
qdrant.tech

redis.com
redis.io

sphinxsearch.com

Technical documentation

cloud.google.com/datastore/docs

qdrant.tech/documentation

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

sphinxsearch.com/docs

Developer

Google

Qdrant

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Sphinx Technologies Inc.

Initial release

2008

2021

2009

2001

Current release

7.2.5, May 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

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

Open Source

GPL version 2, commercial licence available

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

Rust

C++

Server operating systems

hosted

Docker
Linux
macOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

with RediSearch module

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (GQL)

with RediSQL module

SQL-like query language (SphinxQL)

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

proprietary protocol

RESP - REdis Serialization Protocol

Proprietary protocol

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

using Google App Engine

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

Triggers

Callbacks using the Google Apps Engine

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Collection-level replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency, tunable 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

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

The original contents of fields are not stored in the Sphinx index.

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 (IAM)

Key-based 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.