System Design Roadmap 3 - Data and Caching

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/23

flashcard set

Earn XP

Description and Tags

Roadmap.sh system design study block: data and caching.

Last updated 9:50 PM on 7/10/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

24 Terms

1
New cards

Database

A system for storing, querying, and managing persistent data.

2
New cards

SQL vs NoSQL

SQL databases prioritize relational schemas and expressive queries; NoSQL databases optimize for flexible models, scale, or specific access patterns.

3
New cards

RDBMS

A relational database management system that stores data in tables and uses SQL with constraints and transactions.

4
New cards

Key-Value Store

A database that retrieves values by key, useful for caches, sessions, and simple lookups.

5
New cards

Document Store

A database that stores semi-structured documents such as JSON and supports flexible nested data.

6
New cards

Wide Column Store

A distributed database model optimized for large-scale sparse rows and high write throughput.

7
New cards

Graph Database

A database optimized for entities and relationships, useful for traversals such as social graphs or recommendations.

8
New cards

Database Replication

Keeping copies of data on multiple nodes for availability, durability, and read scaling.

9
New cards

Sharding

Splitting data across partitions or nodes so each shard owns a subset of the dataset.

10
New cards

Federation

Splitting databases by function or domain, such as users, products, and orders.

11
New cards

Denormalization

Duplicating or prejoining data to speed reads, usually at the cost of write complexity and consistency work.

12
New cards

SQL Tuning

Improving SQL performance through indexes, query plans, schema changes, batching, and avoiding expensive scans.

13
New cards

Caching

Storing frequently used data in a faster layer to reduce latency and backend load.

14
New cards

Refresh Ahead

Refreshing cached data before it expires so users are less likely to hit stale or missing entries.

15
New cards

Write-Behind Cache

Writes go to the cache first and are asynchronously persisted to the database.

16
New cards

Write-Through Cache

Writes update the cache and database synchronously, keeping them aligned at higher write latency.

17
New cards

Cache-Aside

Application code checks the cache, loads from the database on miss, then populates the cache.

18
New cards

Client Caching

Caching responses in browsers or apps to reduce network calls.

19
New cards

CDN Caching

Caching static or cacheable dynamic content at edge locations.

20
New cards

Web Server Caching

Caching generated responses or assets at the web server layer.

21
New cards

Database Caching

Using database buffer pools, materialized views, or external caches to speed repeated queries.

22
New cards

Application Caching

Keeping computed objects or query results in application memory or a distributed cache.

23
New cards

Cache Invalidation

Removing or refreshing cached entries when underlying data changes.

24
New cards

Cache Stampede

Many clients recompute or refetch the same expired item simultaneously, overloading the backend.