StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. NoSQL Databases
  4. NOSQL Database As A Service
  5. Amazon DynamoDB vs MongoDB

Amazon DynamoDB vs MongoDB

OverviewDecisionsComparisonAlternatives

Overview

Amazon DynamoDB
Amazon DynamoDB
Stacks4.0K
Followers3.2K
Votes195
MongoDB
MongoDB
Stacks96.6K
Followers82.0K
Votes4.1K
GitHub Stars27.7K
Forks5.7K

Amazon DynamoDB vs MongoDB: What are the differences?

Introduction

In this article, we will discuss the key differences between Amazon DynamoDB and MongoDB. Both DynamoDB and MongoDB are popular NoSQL databases, but they have some important distinctions that may impact their suitability for different use cases.

  1. Data Model: One of the key differences between DynamoDB and MongoDB is their data model. DynamoDB is considered a key-value store with support for composite primary keys and secondary indexes. It organizes data into tables, items, and attributes. On the other hand, MongoDB is known for its flexible document-oriented data model. It stores data in BSON (Binary JSON) format, allowing for nested structures, arrays, and richer document-oriented querying capabilities.

  2. Scalability: DynamoDB and MongoDB have different approaches to scalability. DynamoDB is a fully managed service provided by Amazon Web Services (AWS) and automatically scales horizontally to handle high-volume workloads. It offers on-demand and provisioned capacity modes to adjust throughput capacity based on application needs. MongoDB, on the other hand, requires manual setup and configuration of sharding to achieve horizontal scaling. It provides a sharded cluster architecture where data is partitioned across multiple servers.

  3. Performance: When it comes to performance, DynamoDB and MongoDB have slightly different characteristics. DynamoDB is known for its low-latency and high-throughput capabilities. It leverages SSD storage and automatically handles data replication and failover. However, DynamoDB's performance is tied to its provisioned capacity, which may lead to increased costs for maintaining high performance. MongoDB provides good overall performance with flexible indexing options and query optimization techniques. It allows for fine-tuning and optimization of performance based on specific use cases.

  4. Consistency Model: DynamoDB and MongoDB differ in their consistency models. DynamoDB provides two consistency models: eventually consistent reads and strongly consistent reads. Eventually consistent reads allow for lower latency but may return stale data, while strongly consistent reads provide the most up-to-date data with higher latency. MongoDB offers a configurable consistency model, allowing developers to choose between strong consistency and eventual consistency based on their application requirements.

  5. Querying and Indexing: Another significant difference between DynamoDB and MongoDB is their querying and indexing capabilities. DynamoDB supports simple key-value based retrieval and querying using primary keys and secondary indexes. It also provides a Query API for more complex queries. MongoDB, on the other hand, offers a powerful query language with rich functionality, including multi-document transactions, aggregations, and full-text search. MongoDB allows for flexible indexing on different fields and supports geospatial indexing and querying as well.

  6. Cost Model: Finally, DynamoDB and MongoDB have different cost models. DynamoDB pricing is based on provisioned capacity and additional charges for data transfer and backup storage. The costs can increase if the provisioned capacity needs to be scaled up to handle higher workloads. MongoDB, on the other hand, is open-source and can be self-hosted, which may result in lower infrastructure costs. However, if using MongoDB Atlas (MongoDB's fully managed cloud database service), costs will vary based on the chosen plan and usage.

In summary, Amazon DynamoDB and MongoDB differ in their data model, scalability, performance, consistency model, querying and indexing capabilities, and cost model. These differences should be carefully considered when choosing the appropriate database for a specific application or use case.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Amazon DynamoDB, MongoDB

George
George

Student

Mar 18, 2020

Needs adviceonPostgreSQLPostgreSQLPythonPythonDjangoDjango

Hello everyone,

Well, I want to build a large-scale project, but I do not know which ORDBMS to choose. The app should handle real-time operations, not chatting, but things like future scheduling or reminders. It should be also really secure, fast and easy to use. And last but not least, should I use them both. I mean PostgreSQL with Python / Django and MongoDB with Node.js? Or would it be better to use PostgreSQL with Node.js?

*The project is going to use React for the front-end and GraphQL is going to be used for the API.

Thank you all. Any answer or advice would be really helpful!

620k views620k
Comments
Ido
Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k
Comments
Mike
Mike

Mar 20, 2020

Needs advice

We Have thousands of .pdf docs generated from the same form but with lots of variability. We need to extract data from open text and more important - from tables inside the docs. The output of Couchbase/Mongo will be one row per document for backend processing. ADOBE renders the tables in an unusable form.

241k views241k
Comments

Detailed Comparison

Amazon DynamoDB
Amazon DynamoDB
MongoDB
MongoDB

With it , you can offload the administrative burden of operating and scaling a highly available distributed database cluster, while paying a low price for only what you use.

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

Automated Storage Scaling – There is no limit to the amount of data you can store in a DynamoDB table, and the service automatically allocates more storage, as you store more data using the DynamoDB write APIs;Provisioned Throughput – When creating a table, simply specify how much request capacity you require. DynamoDB allocates dedicated resources to your table to meet your performance requirements, and automatically partitions data over a sufficient number of servers to meet your request capacity;Fully Distributed, Shared Nothing Architecture
Flexible data model, expressive query language, secondary indexes, replication, auto-sharding, in-place updates, aggregation, GridFS
Statistics
GitHub Stars
-
GitHub Stars
27.7K
GitHub Forks
-
GitHub Forks
5.7K
Stacks
4.0K
Stacks
96.6K
Followers
3.2K
Followers
82.0K
Votes
195
Votes
4.1K
Pros & Cons
Pros
  • 62
    Predictable performance and cost
  • 56
    Scalable
  • 35
    Native JSON Support
  • 21
    AWS Free Tier
  • 7
    Fast
Cons
  • 4
    Only sequential access for paginate data
  • 1
    Scaling
  • 1
    Document Limit Size
Pros
  • 829
    Document-oriented storage
  • 594
    No sql
  • 554
    Ease of use
  • 465
    Fast
  • 410
    High performance
Cons
  • 6
    Very slowly for connected models that require joins
  • 3
    Not acid compliant
  • 2
    Proprietary query language
Integrations
Amazon RDS for PostgreSQL
Amazon RDS for PostgreSQL
PostgreSQL
PostgreSQL
MySQL
MySQL
SQLite
SQLite
Azure Database for MySQL
Azure Database for MySQL
No integrations available

What are some alternatives to Amazon DynamoDB, MongoDB?

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

InfluxDB

InfluxDB

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase