Versions Compared
Version | Old Version 3 | New Version 4 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
1- Vertical scaling vs Horizontal scaling
2- SQL vs NoSQL
When to consider a NoSQL datastore ?
NoSQL datastore when | Relational database when |
---|---|
High volume of workloads (need latency in milliseconds while performing millions of transactions per second) | Workload volume fits within thousands of transactions per second |
Data is dynamic and frequently changes | Data is highly structured and requires referential integrity |
Relationships can be de-normalized data models | Relationships are expressed through table joins on normalized data models |
Data is expressed without table joins | Data with complex queries and reports |
Data is replicated across geographies and requires finer control over performance, availability and consistency. | Data is centralized or can be replicated regions asynchronously |
For commodity hardware (app deployed in public clouds) | High-End hardware (app deployed to large and high-end hardware) |
Master-slave replication
Read replicas
Consistency models
Database Sharding
Web Tier Stateless
Multiple Data Centers
On this page.
Table of Contents |
---|