DBMS > JanusGraph vs. mSQL vs. Redis vs. SQream DB

System Properties Comparison JanusGraph vs. mSQL vs. Redis vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

mSQL (Mini SQL) is a simple and lightweight RDBMS

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.

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Graph DBMS

Relational DBMS

Key-value store

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

Relational 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

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

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

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

janusgraph.org

hughestech.com.au/products/msql

redis.com
redis.io

sqream.com

Technical documentation

docs.janusgraph.org

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

docs.sqream.com

Developer

Linux Foundation; originally developed as Titan by Aurelius

Hughes Technologies

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SQream Technologies

Initial release

2017

1994

2009

2017

Current release

0.6.3, February 2023

4.4, October 2021

7.2.5, May 2024

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free licenses can be provided

Open Source

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

commercial

Cloud-based only

Only available as a cloud service

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++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
OS X
Unix
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

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, ANSI Standard SQL Types

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

with RediSQL module

yes

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

.Net
JDBC
ODBC

Supported programming languages

Clojure
Java
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

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++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

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

user defined functions in Python

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

Sharding

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

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

via Faunus, a graph analytics engine

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

none

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

Relationships in graphs

Transaction concepts

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

ACID

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

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.