Uber architecture overview in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main architectural style used by Uber for its system design?

Uber uses a microservices architecture, where the system is divided into small, independent services that communicate over the network.

beginner

Why does Uber use microservices instead of a monolithic architecture?

Microservices allow Uber to scale individual components independently, deploy updates faster, and isolate failures to improve reliability.

intermediate

What role does the 'Dispatch Service' play in Uber's architecture?

The Dispatch Service matches riders with nearby drivers by processing location data and availability in real-time.

advanced

How does Uber ensure data consistency across its distributed microservices?

Uber uses event-driven communication with message queues and eventual consistency patterns to synchronize data across services.

intermediate

What is the purpose of the API Gateway in Uber's system?

The API Gateway acts as a single entry point for client requests, routing them to appropriate microservices and handling authentication and rate limiting.

Which architectural style does Uber primarily use?

A Microservices

B Monolithic

C Client-Server

D Peer-to-Peer

Uber uses microservices to build scalable and independent components.

What is the main function of Uber's Dispatch Service?

A Handle notifications

B Process payments

C Store user profiles

D Match riders with drivers

The Dispatch Service matches riders with nearby drivers in real-time.

How does Uber handle communication between microservices?

A Direct database sharing

B File transfers

C Event-driven messaging

D Synchronous HTTP calls only

Uber uses event-driven messaging for asynchronous communication and data consistency.

What is the role of the API Gateway in Uber's architecture?

A Route client requests and handle security

B Store all data

C Manage driver locations

D Process payments

The API Gateway routes requests and manages authentication and rate limiting.

Why is microservices architecture beneficial for Uber?

A It reduces the number of servers needed

B It allows independent scaling and faster deployments

C It simplifies the codebase into one file

D It eliminates the need for databases

Microservices enable independent scaling and faster updates.

Explain the key components of Uber's microservices architecture and how they interact.

Think about how requests flow from users to services and how services communicate.

Describe how Uber achieves scalability and reliability using microservices.

Consider how breaking the system into parts helps handle more users and failures.

Practice

1. What is the main reason Uber uses microservices in its architecture?

easy

A. To reduce the number of servers needed

B. To store all data in a single database for simplicity

C. To avoid using APIs for communication

D. To separate different tasks into independent services for better scalability

Solution

1. Step 1: Understand microservices purpose

   Microservices break a large system into smaller, independent parts to handle specific tasks.

2. Step 2: Relate to Uber's needs

   Uber needs to handle many users and real-time updates, so separating tasks helps scale and manage complexity.

3. Final Answer:

   To separate different tasks into independent services for better scalability -> Option D

4. Quick Check:

   Microservices = Independent scalable services [OK]

Hint: Microservices split tasks for easy scaling and management [OK]

Common Mistakes:

• Thinking microservices mean one big database
• Assuming no APIs are used
• Believing microservices reduce servers directly

2. Which of the following is a correct way Uber's microservices communicate?

easy

A. Using APIs and message queues

B. Direct database queries between services

C. Sharing memory space directly

D. Using FTP to transfer data files

Solution

1. Step 1: Identify communication methods in microservices

   Microservices communicate via APIs (for requests) and message queues (for async events).

2. Step 2: Match with Uber's architecture

   Uber uses APIs and message queues to enable services to talk without tight coupling.

3. Final Answer:

   Using APIs and message queues -> Option A

4. Quick Check:

   Communication = APIs + message queues [OK]

Hint: Microservices talk via APIs and message queues [OK]

Common Mistakes:

• Thinking services query each other's databases
• Assuming shared memory is used
• Believing FTP is used for service communication

3. Consider Uber's ride request flow: User app sends request -> Dispatch service -> Driver service -> Notification service. Which service likely handles real-time driver location updates?

medium

A. Driver service

B. Dispatch service

C. Notification service

D. User app

Solution

1. Step 1: Understand each service role

   User app sends requests, Dispatch matches rides, Driver service manages driver data, Notification sends alerts.

2. Step 2: Identify who tracks driver location

   Driver service manages driver info including real-time location updates.

3. Final Answer:

   Driver service -> Option A

4. Quick Check:

   Driver location updates = Driver service [OK]

Hint: Driver service manages driver data and location [OK]

Common Mistakes:

• Confusing Dispatch with driver location tracking
• Thinking Notification service tracks location
• Assuming User app handles driver location

4. If Uber's Notification service fails to send ride updates, what is the best way to fix it without affecting other services?

medium

A. Restart the entire system including all microservices

B. Fix and restart only the Notification service

C. Merge Notification service with Dispatch service

D. Stop all services to prevent errors

Solution

1. Step 1: Understand microservices isolation

   Each microservice runs independently, so fixing one doesn't require restarting all.

2. Step 2: Apply best practice for failure

   Fix and restart only the failing Notification service to avoid downtime elsewhere.

3. Final Answer:

   Fix and restart only the Notification service -> Option B

4. Quick Check:

   Isolated fixes = Restart single service [OK]

Hint: Fix only the failing microservice to avoid system downtime [OK]

Common Mistakes:

• Restarting all services unnecessarily
• Merging services causing complexity
• Stopping all services causing downtime

5. Uber wants to handle a sudden surge of users during a big event. Which architectural approach best supports this scaling need?

hard

A. Limit user requests to reduce load manually

B. Combine all services into one monolithic app for faster response

C. Use microservices with auto-scaling and load balancing

D. Use a single powerful server to handle all traffic

Solution

1. Step 1: Understand scaling in microservices

   Microservices allow scaling individual parts independently using auto-scaling and load balancing.

2. Step 2: Compare options for surge handling

   Monolithic apps and single servers can't scale easily; limiting users reduces experience.

3. Final Answer:

   Use microservices with auto-scaling and load balancing -> Option C

4. Quick Check:

   Scaling surge = Microservices + auto-scaling [OK]

Hint: Auto-scale microservices to handle traffic spikes smoothly [OK]

Common Mistakes:

• Thinking monolith scales better
• Relying on single server power
• Manually limiting users instead of scaling