DBMS > Amazon DynamoDB vs. MongoDB vs. NebulaGraph

System Properties Comparison Amazon DynamoDB vs. MongoDB vs. NebulaGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

A distributed, linear scalable, high perfomant Graph DBMS

Primary database model

Document store
Key-value store

Document store

Graph DBMS

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

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

Score	79.30
Rank	#15	Overall
	#3	Document stores
	#2	Key-value stores

Score	402.51
Rank	#5	Overall
	#1	Document stores

Score	1.75
Rank	#128	Overall
	#11	Graph DBMS

Website

aws.amazon.com/dynamodb

www.mongodb.com

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

Technical documentation

docs.aws.amazon.com/dynamodb

www.mongodb.com/docs/manual

docs.nebula-graph.io

Developer

Amazon

MongoDB, Inc

Vesoft Inc.

Initial release

2012

2009

2019

Current release

7.0.5, January 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

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

Apache Version 2.0 + Common Clause 1.0

Cloud-based only

Only available as a cloud service

yes

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 Flex @ STACKIT offers managed MongoDB Instances with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux

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.

Strong typed schema

Typing

predefined data types such as float or date

yes

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

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

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.

SQL

Support of SQL

Read-only SQL queries via the MongoDB Atlas SQL Interface

SQL-like query language

APIs and other access methods

RESTful HTTP API

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C++
Go
Java
PHP
Python

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

yes

by integration with AWS Lambda

yes

in MongoDB Atlas only

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.

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Causal Clustering using Raft protocol

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Relationships in graphs

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

Multi-document ACID Transactions with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional, enabled by default

yes

using RocksDB

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 can be defined via the AWS Identity and Access Management (IAM)

Access rights for users and roles

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.