Choosing relational vs NoSQL managed databases
WHAT IT TESTS: data model and access pattern fit. OUTLINE: choose relational for complex relationships, joins, flexible queries, and strong transactions; choose NoSQL for known access patterns needing massive horizontal scale.
WHAT IT TESTS: matching a database to data model, access patterns, and scale. ANSWER OUTLINE: choose a relational service like RDS when you have structured, related data, need joins and ad hoc queries, and want strong ACID transactions and a fixed schema. Choose a NoSQL service like DynamoDB when access patterns are well known and simple, the schema is flexible, and you need near-limitless horizontal scale with predictable single-digit latency. Drivers are query flexibility, consistency needs, and scale.
Read the original → interview
- #databases
- #rds
- #dynamodb
- #nosql
- #cloud
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.