InterviewStack.io LogoInterviewStack.io

Scaling Fundamentals and Concepts Questions

Core concepts required to reason about scaling decisions and to communicate clear approaches. Topics include the difference between vertical and horizontal scaling and their trade offs; stateless versus stateful service design and why statelessness enables horizontal scaling; basic load balancing and request distribution strategies; when and how to apply caching replication and partitioning; simple autoscaling concepts and common metrics used to trigger scaling; how to identify common bottlenecks and apply pragmatic mitigations; and fundamental trade offs between latency throughput cost and complexity. This topic tests conceptual clarity and the ability to map requirements to simple scaling approaches.

MediumTechnical
70 practiced
Implement a token bucket rate limiter in Python. The limiter should support parameters: capacity (max_tokens), refill_rate (tokens per second), and a method allow(n=1) that returns True if tokens were available and consumes them, otherwise False. Provide single-process code and explain how this design would need to change for a distributed deployment.
EasyTechnical
76 practiced
Define stateless and stateful service design in practical SRE terms. Explain why statelessness enables horizontal scaling, what operational patterns support stateless services (e.g., external state stores, tokens), and list trade-offs when converting a stateful service to stateless.
MediumSystem Design
59 practiced
Design a CDN and edge caching approach for a global application that serves static assets and dynamic localized content. Cover cache keying, TTLs per content type, purge/invalidations, origin protection, geo-routing, and measurement to prove latency and cache-hit improvements.
EasyTechnical
63 practiced
In plain SRE terms, explain caching, replication and partitioning (sharding). For each technique give a short example use-case, the main trade-offs (consistency, memory/cost, complexity), and a one-line rule-of-thumb for when to apply it in a service architecture.
MediumTechnical
54 practiced
You see rising request latency and backend queue growth during a spike. Provide a step-by-step triage plan to identify the bottleneck: which metrics and dashboards to check (CPU, disk IO, network, thread pools, DB latency), tools you would use, and immediate mitigations to restore availability.

Unlock Full Question Bank

Get access to hundreds of Scaling Fundamentals and Concepts interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.