DBMS > AnzoGraph DB vs. Drizzle vs. Google Cloud Firestore vs. Redis vs. TerminusDB

System Properties Comparison AnzoGraph DB vs. Drizzle vs. Google Cloud Firestore vs. Redis vs. TerminusDB

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

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

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.

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

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

Graph 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

Document store
RDF store

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

Score	0.22
Rank	#301	Overall
	#26	Graph DBMS
	#14	RDF stores

Score	6.53
Rank	#54	Overall
	#9	Document stores

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

Score	0.15
Rank	#326	Overall
	#30	Graph DBMS

Website

cambridgesemantics.com/anzograph

firebase.google.com/products/firestore

redis.com
redis.io

terminusdb.com

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

firebase.google.com/docs/firestore

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

terminusdb.github.io/terminusdb/#

Developer

Cambridge Semantics

Drizzle project, originally started by Brian Aker

Google

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

DataChemist Ltd.

Initial release

2018

2008

2017

2009

2018

Current release

2.3, January 2021

7.2.4, September 2012

7.2.5, May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

free trial version available

Open Source

GNU GPL

commercial

Open Source

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

Open Source

GPL V3

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.

Implementation language

C++

Prolog, Rust

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

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

yes

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

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

with proprietary extensions

with RediSQL module

SQL-like query language (WOQL)

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

JDBC

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C++
Java
Python

C
C++
Java
PHP

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
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

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes, Firebase Rules & Cloud Functions

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

yes

Triggers

hooks for callbacks inside the server can be used.

yes, with Cloud Functions

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Multi-source replication
Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Using Cloud Dataflow

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

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

not needed in graphs

yes

Transaction concepts

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

ACID

yes

Atomic execution of command blocks and scripts and optimistic locking

ACID

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 journaling

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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

Role-based access control

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.