Need advice about which tool to choose?Ask the StackShare community!
Amazon DynamoDB vs Redis: What are the differences?
What is Amazon DynamoDB? Fully managed NoSQL database service. All data items are stored on Solid State Drives (SSDs), and are replicated across 3 Availability Zones for high availability and durability. With DynamoDB, 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.
What is Redis? An in-memory database that persists on disk. Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.
Amazon DynamoDB and Redis are primarily classified as "NoSQL Database as a Service" and "In-Memory Databases" tools respectively.
"Predictable performance and cost" is the primary reason why developers consider Amazon DynamoDB over the competitors, whereas "Performance" was stated as the key factor in picking Redis.
Redis is an open source tool with 37.1K GitHub stars and 14.3K GitHub forks. Here's a link to Redis's open source repository on GitHub.
reddit, Instacart, and Slack are some of the popular companies that use Redis, whereas Amazon DynamoDB is used by Lyft, New Relic, and Sellsuki. Redis has a broader approval, being mentioned in 3239 company stacks & 1732 developers stacks; compared to Amazon DynamoDB, which is listed in 429 company stacks and 173 developer stacks.
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?
Hi, Akash,
I wouldn't make this decision without lots more information. Cloud Firestore has a much richer metamodel (document-oriented) than Dynamo (key-value), and Dynamo seems to be particularly restrictive. That is why it is so fast. There are many needs in most applications to get lightning access to the members of a set, one set at a time. Dynamo DB is a great choice. But, social media applications generally need to be able to make long traverses across a graph. While you can make almost any metamodel act like another one, with your own custom layers on top of it, or just by writing a lot more code, it's a long way around to do that with simple key-value sets. It's hard enough to traverse across networks of collections in a document-oriented database. So, if you are moving, I think a graph-oriented database like Amazon Neptune, or, if you might want built-in reasoning, Allegro or Ontotext, would take the least programming, which is where the most cost and bugs can be avoided. Also, managed systems are also less costly in terms of people's time and system errors. It's easier to measure the costs of managed systems, so they are often seen as more costly.
Pros of Amazon DynamoDB
- Predictable performance and cost62
- Scalable56
- Native JSON Support35
- AWS Free Tier21
- Fast7
- No sql3
- To store data3
- Serverless2
- No Stored procedures is GOOD2
- ORM with DynamoDBMapper1
- Elastic Scalability using on-demand mode1
- Elastic Scalability using autoscaling1
- DynamoDB Stream1
Pros of Redis
- Performance884
- Super fast541
- Ease of use512
- In-memory cache443
- Advanced key-value cache323
- Open source193
- Easy to deploy182
- Stable164
- Free155
- Fast121
- High-Performance42
- High Availability40
- Data Structures34
- Very Scalable32
- Replication24
- Pub/Sub22
- Great community22
- "NoSQL" key-value data store19
- Hashes15
- Sets13
- Sorted Sets11
- Lists10
- BSD licensed9
- NoSQL9
- Integrates super easy with Sidekiq for Rails background8
- Async replication8
- Bitmaps8
- Open Source7
- Keys with a limited time-to-live7
- Lua scripting6
- Strings6
- Awesomeness for Free5
- Hyperloglogs5
- Written in ANSI C4
- LRU eviction of keys4
- Networked4
- Outstanding performance4
- Runs server side LUA4
- Transactions4
- Feature Rich4
- Performance & ease of use3
- Data structure server3
- Object [key/value] size each 500 MB2
- Simple2
- Scalable2
- Temporarily kept on disk2
- Dont save data if no subscribers are found2
- Automatic failover2
- Easy to use2
- Existing Laravel Integration2
- Channels concept2
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon DynamoDB
- Only sequential access for paginate data4
- Scaling1
- Document Limit Size1
Cons of Redis
- Cannot query objects directly15
- No secondary indexes for non-numeric data types3
- No WAL1
Sign up to add or upvote consMake informed product decisions
What is Amazon DynamoDB?
What is Redis?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Amazon DynamoDB?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Amazon DynamoDB?
What tools integrate with Redis?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+9
+8
+17
+9
+12+23+17