DBMS > MongoDB vs. MySQL vs. NebulaGraph vs. Redis

System Properties Comparison MongoDB vs. MySQL vs. NebulaGraph vs. Redis

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

Widely used open source RDBMS

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.

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Key-value store

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

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

Document store
Spatial DBMS

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	421.65
Rank	#5	Overall
	#1	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.14
Rank	#120	Overall
	#10	Graph DBMS

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

Website

www.mongodb.com

www.mysql.com

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

redis.com
redis.io

Technical documentation

www.mongodb.com/docs/manual

dev.mysql.com/doc

docs.nebula-graph.io

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

Developer

MongoDB, Inc

Oracle

since 2010, originally MySQL AB, then Sun

Vesoft Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2009

1995

2019

2009

Current release

6.0.7, June 2023

8.4.0, April 2024

7.2.4, January 2024

License

Commercial or Open Source

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0 + Common Clause 1.0

Open Source

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

Cloud-based only

Only available as a cloud service

MongoDB available as DBaaS (MongoDB Atlas)

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

MongoDB Atlas: Global multi-cloud database with unmatched data distribution and mobility across AWS, Azure, and Google Cloud, built-in automation for resource and workload optimization, and so much more.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

C++

C and C++

C++

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

yes

Strong typed schema

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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.

yes

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

Read-only SQL queries via the MongoDB Atlas SQL Interface

yes

with proprietary extensions

SQL-like query language

with RediSQL module

APIs and other access methods

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

ADO.NET
JDBC
ODBC
Proprietary native 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

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.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

Server-side scripts

Stored procedures

JavaScript

yes

proprietary syntax

user defined functions

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

Triggers

yes

in MongoDB Atlas only

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

Multi-source replication
Source-replica replication

Causal Clustering using Raft protocol

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

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

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

Multi-document ACID Transactions with snapshot isolation

ACID

not for MyISAM storage engine

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

optional, enabled by default

yes

using RocksDB

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

yes

In-memory storage engine introduced with MongoDB version 3.2

yes

User concepts

Access control

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

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

MongoDB provides an integrated suite of cloud database and data services to accelerate...
» more

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

Competitive advantages

Built around the flexible document data model and unified API, MongoDB is a developer...
» more

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

Typical application scenarios

AI-enriched intelligent apps (Continental, Telefonica, Iron Mountain) Internet of...
» more

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

Key customers

ADP, Adobe, Amadeus, AstraZeneca, Auto Trader, Barclays, BBVA, Bosch, Cisco, CERN,...
» more

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

Market metrics

Hundreds of millions downloads, over 150,000+ Atlas clusters provisioned every month...
» more

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

Licensing and pricing models

MongoDB database server: Server-Side Public License (SSPL) . Commercial licenses...
» more

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.