Uber architecture overview in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the main component responsible for matching riders with drivers.

Microservices

The core service that connects riders and drivers in Uber's system is called the [1] service.

Drag options to blanks, or click blank then click option'

AAuthentication

BBilling

CNotification

DMatching

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing billing or notification services with the matching service.

The Matching service is responsible for pairing riders with nearby drivers efficiently.

2fill in blank

medium

Complete the code to specify the database type used for storing trip history in Uber's architecture.

Microservices

Uber uses a [1] database to store detailed trip history and user data for durability and queries.

Drag options to blanks, or click blank then click option'

AIn-memory

BGraph

CRelational

DTime-series

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing in-memory or time-series databases for persistent trip data.

Relational databases are used to store structured data like trip history with strong consistency.

3fill in blank

hard

Fix the error in naming the Uber service responsible for handling payments.

Microservices

The service that processes payments and handles transactions is called the [1] service.

Drag options to blanks, or click blank then click option'

APayment

BNotification

CMatching

DRouting

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing payment service with notification or routing services.

The Payment service manages all financial transactions between riders and drivers.

4fill in blank

hard

Fill both blanks to complete the description of Uber's architecture components.

Microservices

The [1] service tracks real-time locations, while the [2] service calculates the best routes for drivers.

Drag options to blanks, or click blank then click option'

ALocation

BBilling

CRouting

DAuthentication

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing billing or authentication with location or routing.

The Location service monitors driver and rider positions. The Routing service finds optimal paths.

5fill in blank

hard

Fill all three blanks to complete the key components in Uber's microservices architecture.

Microservices

The [1] service authenticates users, the [2] service sends ride updates, and the [3] service manages fare calculations.

Drag options to blanks, or click blank then click option'

AAuthentication

BNotification

CBilling

DMatching

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing matching with billing or notification services.

Authentication verifies users, Notification sends updates, and Billing calculates fares.

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