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 RocksDB

Amazon DynamoDB vs RocksDB

OverviewDecisionsComparisonAlternatives

Overview

Amazon DynamoDB
Amazon DynamoDB
Stacks4.0K
Followers3.2K
Votes195
RocksDB
RocksDB
Stacks141
Followers290
Votes11
GitHub Stars30.9K
Forks6.6K

Amazon DynamoDB vs RocksDB: What are the differences?

Introduction

In this article, we will compare Amazon DynamoDB and RocksDB, two popular database systems. We will highlight the key differences between them and provide a brief description of each difference.

  1. Data Model: Amazon DynamoDB is a NoSQL database that supports document, key-value, and wide-column data models. It allows flexible schema design and is suitable for applications that require high scalability. On the other hand, RocksDB is a key-value store database that follows a simple key-value data model. It is optimized for read-heavy workloads and offers high-performance data storage and retrieval.

  2. Data Distribution and Scalability: DynamoDB is a fully managed distributed database that automatically partitions data across multiple servers for high availability and scalability. It transparently handles the distribution of data and workload across these servers. In contrast, RocksDB operates as a single-node database and does not provide built-in mechanisms for data distribution or scaling. It can be used as a component within a larger distributed system.

  3. Consistency Models: DynamoDB offers both strong consistency and eventual consistency models. Strong consistency ensures that all reads reflect the latest write, while eventual consistency allows for faster and more scalable operations at the cost of potential data inconsistency. RocksDB, on the other hand, does not provide built-in support for consistency models. Consistency needs to be implemented at the application level when using RocksDB.

  4. Data Persistence: DynamoDB automatically replicates data across multiple data centers for durability and fault tolerance. It provides a managed service that takes care of data persistence. In contrast, RocksDB is an in-memory database and requires additional measures like write-ahead logs or persistent storage engines to ensure data persistence and durability.

  5. Indexing and Querying: DynamoDB supports secondary indexes, allowing efficient querying of data based on different attributes. It also provides a query language for filtering and sorting data. RocksDB, being a key-value store, does not provide native support for secondary indexes or complex querying. Querying in RocksDB is primarily based on key lookups or range scans.

  6. Transaction Support: DynamoDB supports atomic transactions that provide consistency and isolation guarantees. It allows developers to group multiple operations into a transaction and ensures that they are either all executed or none are. RocksDB, being an embedded database, does not offer built-in transaction support. Transactional behavior needs to be implemented manually by the application when using RocksDB.

In summary, Amazon DynamoDB and RocksDB differ in terms of their data models, data distribution and scalability, consistency models, data persistence, indexing and querying capabilities, and transaction support. DynamoDB provides a managed, scalable, and highly available distributed database service, while RocksDB is optimized for high-performance key-value storage in single-node environments.

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, RocksDB

Doru
Doru

Solution Architect

Jun 9, 2019

ReviewonAmazon DynamoDBAmazon DynamoDB

I use Amazon DynamoDB because it integrates seamlessly with other AWS SaaS solutions and if cost is the primary concern early on, then this will be a better choice when compared to AWS RDS or any other solution that requires the creation of a HA cluster of IaaS components that will cost money just for being there, the costs not being influenced primarily by usage.

1.38k views1.38k
Comments
akash
akash

Aug 27, 2020

Needs adviceonCloud FirestoreCloud FirestoreFirebase Realtime DatabaseFirebase Realtime DatabaseAmazon DynamoDBAmazon DynamoDB

We are building a social media app, where users will post images, like their post, and make friends based on their interest. We are currently using Cloud Firestore and Firebase Realtime Database. We are looking for another database like Amazon DynamoDB; how much this decision can be efficient in terms of pricing and overhead?

199k views199k
Comments

Detailed Comparison

Amazon DynamoDB
Amazon DynamoDB
RocksDB
RocksDB

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.

RocksDB is an embeddable persistent key-value store for fast storage. RocksDB can also be the foundation for a client-server database but our current focus is on embedded workloads. RocksDB builds on LevelDB to be scalable to run on servers with many CPU cores, to efficiently use fast storage, to support IO-bound, in-memory and write-once workloads, and to be flexible to allow for innovation.

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
Designed for application servers wanting to store up to a few terabytes of data on locally attached Flash drives or in RAM;Optimized for storing small to medium size key-values on fast storage -- flash devices or in-memory;Scales linearly with number of CPUs so that it works well on ARM processors
Statistics
GitHub Stars
-
GitHub Stars
30.9K
GitHub Forks
-
GitHub Forks
6.6K
Stacks
4.0K
Stacks
141
Followers
3.2K
Followers
290
Votes
195
Votes
11
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
  • 5
    Very fast
  • 3
    Made by Facebook
  • 2
    Consistent performance
  • 1
    Ability to add logic to the database layer where needed
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, RocksDB?

MongoDB

MongoDB

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.

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.

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