You are asked systems/design-concepts questions based on real product scenarios. For each scenario below:
You have a read-heavy service with hot keys and strict p99 latency. How would you use a cache (e.g., Redis) and what cache strategy would you pick (cache-aside, read-through, write-through, write-back)? How do you prevent cache stampede and handle invalidation?
A user can place an order and you must avoid overselling inventory under high concurrency.
You need to process events (e.g., payments, notifications) reliably without slowing down the request path. When do you pick:
Pick a primary storage solution and justify:
What metrics and dashboards would you define to prove the system scales? How would you debug rising tail latency?
Login required