Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

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.

  • No labels