RDS vs DynamoDB — how do you choose between them?
Reviewed by Gurusankar M.
Short Answer
RDS (relational) for complex queries, joins, transactions, and flexible ad-hoc access — scales vertically + read replicas. DynamoDB (NoSQL key-value) for predictable access patterns needing single-digit-ms latency at massive scale — but you must model around known queries (no ad-hoc joins). Choose by query flexibility vs scale.
On this page
Concept Made Simple
Coffee Chat Question
“RDS vs DynamoDB — how do you choose between them?”
Remember It Faster
Mind Map Answer
- RDS
- joins, transactions, ad-hoc queries
- DynamoDB
- known access patterns, huge scale, ms latency
- Scale
- RDS vertical+replicas; DDB horizontal
- Trap
- DDB with unknown/ad-hoc queries
Think Beyond the Expected
What If?
When does DynamoDB become painful?
When your access patterns change or need ad-hoc queries/joins — DynamoDB requires you to design tables (and GSIs) around specific queries up front. New query needs may force a new index or a full redesign. If flexibility matters more than extreme scale, RDS is the safer choice.
Real World
Teams pick RDS for rich transactional/reporting workloads and DynamoDB for high-scale, well-understood access (sessions, carts, event stores); the mistake is choosing DynamoDB for evolving, query-flexible domains.
Interviewer's Expectation
Keywords they're listening for:
- relational vs key-value
- joins/transactions vs scale/latency
- known access patterns for DDB
- scaling models
- GSIs
Common Mistakes
- DynamoDB for ad-hoc/unknown queries
- RDS for extreme write scale without sharding
- Ignoring access-pattern modeling for DDB
Best Practices
- RDS for query flexibility/transactions
- DynamoDB for scale + known patterns
- Model DynamoDB around queries first
Follow-up Questions
- What is a Global Secondary Index?
- How does DynamoDB scale vs RDS?
- When would you use both together?
Continue Learning with AI
Take this question deeper with your favourite AI assistant. Pick a depth, copy the prompt, or open it directly — AI is your learning companion, not a shortcut.
Plain-language foundations
I'm preparing for a software engineering interview and want to understand this from scratch, as a beginner. Topic: DynamoDB (AWS) Interview question: "RDS vs DynamoDB — how do you choose between them?" Please: 1. Explain the core idea in simple, plain language, using an everyday analogy. 2. Define any technical terms you use. 3. Walk through one small, concrete example. 4. Finish with a single sentence I can easily remember. Keep the tone friendly and assume I'm new to this topic.
Was this answer helpful?
Affiliate links
Tools for Your Developer Workspace
Equipment for a comfortable, productive setup.
As an Amazon Associate I earn from qualifying purchases.
- MonitorView on Amazon : BenQ EW2790U 27-inch Monitor (opens in a new tab)
BenQ EW2790U 27-inch Monitor
- LaptopView on Amazon : Acer Aspire One Laptop (opens in a new tab)
Acer Aspire One Laptop
- Office ChairView on Amazon : Wakefit Gravita Ergonomic Office Chair (opens in a new tab)
Wakefit Gravita Ergonomic Office Chair