Scalability Patterns and Techniques Questions

Scaling a system to handle growth in traffic and data: horizontal versus vertical scaling, statelessness, sharding and partitioning strategies, read replicas, and connection pooling. Covers capacity estimation, identifying bottlenecks, and the tradeoffs each scaling axis introduces. The general toolkit for taking a design from thousands to millions of users.

EasyTechnical
25 practiced

When should you reach for asynchronous processing in a cloud architecture? Give examples of tasks that belong on a queue, the benefits and trade-offs (latency, throughput, complexity), and how you'd choose between a simple message queue, a pub/sub system, and a streaming platform for different workloads.

MediumTechnical
26 practiced

Design an operational plan and technical implementation to reshard a live sharded database with minimal downtime. Cover choosing the new shard key or shard count, the data-migration strategy (online migration, dual writes, change-data-capture), routing updates, throttling the migration, validation steps, and your rollback procedure.

MediumSystem Design
26 practiced

Design sharding for a real-time pub/sub service that has a very large number of channels. Compare client-side sharding, where clients pick their partition, against server-side partitioning, where the broker assigns it. Discuss rebalancing cost, fairness, latency, and client churn from mobile users with intermittent connectivity, and recommend an approach for a client base that is mostly mobile and frequently offline.

MediumTechnical
26 practiced

Your service is stateful and stores per-user ephemeral session data in memory. Walk through three practical approaches to scale it horizontally without breaking correctness: sticky sessions, active-active replication, and externalizing the state. For each, describe the operational complexity, failure modes, and performance characteristics.

EasyTechnical
34 practiced

Your relational database allows a maximum of 500 concurrent connections. Your application runs on 25 identical JVM instances plus 3 background job workers. Walk through how you'd compute a safe default connection-pool size per instance, the factors you'd weigh, and your recommended pool size. What would you monitor, and what would you do if you saw connection saturation in production?

Unlock Full Question Bank

Get access to all Scalability Patterns and Techniques interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.