DBMS > Apache Druid vs. Google Cloud Datastore vs. NebulaGraph vs. Redis vs. SwayDB

System Properties Comparison Apache Druid vs. Google Cloud Datastore vs. NebulaGraph vs. Redis vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

A distributed, linear scalable, high perfomant Graph DBMS

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.

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS
Time Series DBMS

Document store

Graph DBMS

Key-value store

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

Key-value store

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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.14
Rank	#120	Overall
	#10	Graph DBMS

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

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

druid.apache.org

cloud.google.com/datastore

github.com/vesoft-inc/nebula
www.nebula-graph.io

redis.com
redis.io

swaydb.simer.au

Technical documentation

druid.apache.org/docs/latest/design

cloud.google.com/datastore/docs

docs.nebula-graph.io

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

Developer

Apache Software Foundation and contributors

Google

Vesoft Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Simer Plaha

Initial release

2012

2008

2019

2009

2018

Current release

29.0.1, April 2024

7.2.4, January 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache Version 2.0 + Common Clause 1.0

Open Source

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

Open Source

GNU Affero GPL V3.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

Java

C++

Scala

Server operating systems

Linux
OS X
Unix

hosted

Linux

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-less columns are supported

schema-free

Strong typed schema

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

Nebula Graph internally uses the Key-Value store RocksDB for persistency. The vertices, edges, and their properties are stored as Key while their values are stored as Value. The primary indexes are per Key and secondary indexes are per Value.

yes

with RediSearch module

SQL

Support of SQL

SQL for querying

SQL-like query language (GQL)

SQL-like query language

with RediSQL module

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

Browser interface
console (shell)
Cypher Query Language
GO Object Graph Mapper
Java Object Graph Mapper
NGBatis

ORM framework for NebulaGraph and Spring-Boot
Proprietary native API
Python Object Graph Mapper
Query language nGQL

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

.Net
C++
Go
Java
PHP
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

Java
Kotlin
Scala

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

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

manual/auto, time-based

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication using Paxos

Causal Clustering using Raft protocol

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

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.

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

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Atomic execution of command blocks and scripts and optimistic locking

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

using RocksDB

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.

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

Role-based access control

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

NebulaGraph is a truly distributed, linearly scalable, lightning-fast graph database,...
» more

Competitive advantages

NebulaGraph boasts the world's only graph database solution that is able to host...
» more

Typical application scenarios

Social networking Fraud detection Knowledge graph Data warehouse management Anti...
» more

Key customers

Companies from a variety of industries have implemented NebulaGraph Database in production,...
» more

Market metrics

At our very early stage, NebulaGraph has already received over 10,000 stars on GitHub...
» more

Licensing and pricing models

NebulaGraph is open source and free to use under Apache 2.0 license.
» 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.