Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
34 results across 1 active filter
Page 1 of 2
Explains rate-limit identity, endpoint cost, login and suggestion throttles, Redis counters, user experience, and observability.
Compares caching response-shaped read models with caching domain entities or raw database objects.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Explains how TTL choices balance freshness, load reduction, user expectations, and operational safety.
Compares cache-aside, read-through, and write-through by read and write ownership, freshness, failure behavior, invalidation, fallback, stampede control, and operational complexity.
Explains when local process memory is enough and when shared Redis-style caching is worth the extra dependency.
Compares Redis pub/sub with durable queues when broadcasting cache invalidation or refresh events.
Explains how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
Designs dashboard APIs with precomputed metrics, freshness rules, query cost control, and drill-down support.
Designs feature flag storage, targeting, safe defaults, auditability, and rollout observability for backend behavior.
Designs tenant isolation across API, data, cache, background jobs, search, and admin access.
Designs an activity feed with event capture, fan-out strategy, pagination, privacy, and read performance.
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Designs draft, review, publish, rollback, and audit behavior for content managed by editors and admins.
Designs layered public API protection with caller identity, quotas, burst limits, abuse signals, and client-friendly responses.
Designs live updates with polling, server-sent events, or WebSockets while preserving authorization, ordering, scale, and fallback behavior.
Designs search and filtering with controlled query contracts, indexing, pagination, ranking, and operational limits.
Designs a settings service with defaults, validation, scoped preferences, caching, and safe rollout of new settings.
Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Explains when stale cache reads are acceptable, when they are dangerous, and how to make freshness visible.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.
Explains Redis memory pressure, eviction policies, key sizing, TTL discipline, and what happens when the cache is full.
Explains how an API behaves when Redis is unavailable and which cache usages can safely fall back.