Design a Authentication for Adobe
Last updated: February 23, 2026
Quick Overview
Design a real-time authentication system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Adobe
February 23, 202643
11
4,610 solved
Design a real-time authentication system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
This is a common system design question asked during Onsite at Adobe. The interviewer expects you to demonstrate your ability to design large-scale distributed systems, make well-reasoned trade-offs, and communicate your thought process clearly. Adobe values engineers who can think about scalability from day one.
What the Interviewer Expects
- Drive the design discussion proactively with minimal interviewer guidance
- Perform detailed capacity estimation and use it to inform design decisions
- Design for global scale with multi-region deployment and data consistency
- Deep dive into 2-3 critical components with implementation-level detail
- Address complex trade-offs: CAP theorem, eventual consistency, conflict resolution
- Discuss operational excellence: deployment strategy, chaos engineering, SLOs/SLIs
- Propose a phased rollout plan from MVP to full-scale system
Key Topics to Cover
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- 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?
- What would the deployment pipeline look like for this system?
- How would you implement rate limiting to protect the system?
- How would you handle a region-wide outage?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
Functional Requirements
- User Authentication: Users should be able to log in using email/password, multi-factor authentication (MFA), or third-party providers (OAuth).
- **Session Managemen...
Capacity Estimation
To estimate the capacity:
- User Base: Assume 100 million users globally.
- Daily Active Users (DAU): Assume 10% of users authenticate daily, which is 10 million.
- Peak Load: At peak time...