Building Blocks for System Designs
Building blocks are the standard components that most architectures reuse. On the network side they include DNS, load balancers, reverse proxies and CDNs. On the storage side they include the engines under databases, such as B-trees and log-structured merge trees, which shape read and write performance.
Stage: Fundamentals · Part of the System Design roadmap · Last reviewed 19 November 2026
What to learn in Building Blocks
- Explain what a load balancer does and compare round robin with least connections
- Describe how a CDN reduces latency for static content
- Distinguish TCP from UDP and know when each fits
- Compare B-tree and LSM-tree storage for write-heavy workloads
- Explain how an index speeds reads at a cost to writes
- Place a reverse proxy in front of application servers
Building Blocks interview questions
What is the difference between a Layer 4 and Layer 7 load balancer?
A Layer 4 balancer routes using IP addresses and ports without reading the payload, making it fast. A Layer 7 balancer understands HTTP, so it can route by path, header or cookie and terminate TLS, at higher processing cost.
Why are LSM trees good for write-heavy workloads?
An LSM tree buffers writes in memory and flushes them to disk as sorted files appended sequentially, which is much cheaper than random in-place updates. Background compaction merges files later, trading some read cost for write throughput.
Where Building Blocks fits in the System Design roadmap
Building Blocks belongs to the Fundamentals stage (intermediate level), which takes about 32 hours. Think in systems.
Other units in this stage
Back to the full System Design roadmap