Build a multi-tenant Authentication Pipeline

Last updated: March 26, 2026

Quick Overview

Design a multi-tenant authentication system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Google
System Design
Software Engineer
Google
March 26, 2026
Software Engineer
System Design Round
System Design
Medium

68

12

4,492 solved


Design a multi-tenant authentication system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Google asks this during the System Design Round to assess your architectural thinking. They want to see how you decompose a complex problem, choose appropriate technologies, and reason about failure modes. Strong candidates proactively discuss monitoring, alerting, and operational concerns.

What the Interviewer Expects
  • Systematically gather requirements and estimate capacity (QPS, storage, bandwidth)
  • Design a scalable architecture with clear component responsibilities
  • Make well-reasoned database and caching decisions with trade-off analysis
  • Address consistency vs availability trade-offs specific to the use case
  • Discuss partitioning strategy, replication, and data modeling
  • Cover failure handling, monitoring, and alerting strategies
Key Topics to Cover
Security and authentication
Consistency models and replication
API design and rate limiting
Partitioning and sharding strategies
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How would you handle schema migrations with zero downtime?
  • How would you handle a region-wide outage?
  • What happens if one of your database nodes goes down?
  • How would you optimize costs as the system scales?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements

Functional Requirements

  1. Multi-Tenant Support: The system should support multiple tenants with isolated user data.
  2. User Authentication: Provide mechanisms for user login, registration...
Capacity Estimation

Assuming Google has approximately 1 billion users, with 10% active daily users:

  • Active Users: 100 million
  • QPS Calculation: If each user makes 5 authentication requests per day:
    • Total d...

Submit Your Answer
Markdown supported

Related Questions