DBMS > Dgraph vs. Google Cloud Bigtable vs. Redis vs. Tarantool vs. TinkerGraph

System Properties Comparison Dgraph vs. Google Cloud Bigtable vs. Redis vs. Tarantool vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Graph DBMS

Key-value store
Wide column store

Key-value store

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

Document store
Key-value store
Relational DBMS

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

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

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

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

dgraph.io

cloud.google.com/bigtable

redis.com
redis.io

www.tarantool.io

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

dgraph.io/docs

cloud.google.com/bigtable/docs

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

www.tarantool.io/en/doc

Developer

Dgraph Labs, Inc.

Google

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2016

2015

2009

2008

2009

Current release

7.2.5, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

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

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache 2.0

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

C and C++

Java

Server operating systems

Linux
OS X
Windows

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

BSD
Linux
macOS

Data scheme

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

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

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

SQL

Support of SQL

with RediSQL module

Full-featured ANSI SQL support

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

proprietary protocol

RESP - REdis Serialization Protocol

Open binary protocol

TinkerPop 3

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Go
Java
JavaScript (Node.js)
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
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Groovy
Java

Server-side scripts

Stored procedures

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

Lua, C and SQL stored procedures

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

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

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Atomic single-row operations

Atomic execution of command blocks and scripts and optimistic locking

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes, write ahead logging

optional

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

Planned for future releases

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.