System Design: Designing a Food Delivery App (Uber Eats / DoorDash)

System Design: Designing a Food Delivery App

Mental Model

Connecting isolated components into a resilient, scalable, and observable distributed web.

A food delivery platform (like Uber Eats, DoorDash, or Grab) is more than just an e-commerce site. It is a Three-Sided Marketplace that must coordinate between Customers, Restaurants, and Couriers (Drivers) in real-time, all while managing a complex logistical window (the food is only hot for 30 minutes).

1. Core Requirements

graph LR
    Producer[Producer Service] -->|Publish Event| Kafka[Kafka / Event Bus]
    Kafka -->|Consume| Consumer1[Consumer Group A]
    Kafka -->|Consume| Consumer2[Consumer Group B]
    Consumer1 --> DB1[(Primary DB)]
    Consumer2 --> Cache[(Redis)]

• Order Management: Taking orders and managing the lifecycle (Created -> Accepted -> Prepared -> Picked Up -> Delivered).
• Inventory/Menu: Restaurants updating their menus and stock in real-time.
• Courier Dispatching: Efficiently matching an order with the best courier.
• Tracking: Customers seeing the courier's location in real-time.

2. The Order State Machine

The state of an order is the source of truth for all three parties. We use a State Machine to ensure valid transitions:

• PLACED -> ACCEPTED_BY_RESTAURANT -> PREPARING -> READY_FOR_PICKUP -> OUT_FOR_DELIVERY -> DELIVERED.
• Consistency: Use a relational database (PostgreSQL) for order state to ensure ACID compliance during transitions.

3. Courier Dispatching (The Core Challenge)

Matching an order with a courier is an optimization problem.

• The Process:
  1. An order is READY_FOR_PICKUP.
  2. The system identifies available couriers within a 3-5km radius using Geohashing (like in our Yelp/Uber articles).
  3. The Dispatch Service ranks couriers based on distance, vehicle type, and historical performance.
  4. It sends a "Gig Request" to the top-ranked courier. If they reject, it moves to the next.

4. Real-time Location Tracking

• Ingestion: Couriers send GPS pings every 5 seconds via WebSockets or gRPC.
• Processing:Apache Kafka buffers these pings.
• Storage: Only the "Latest Location" is stored in Redis for fast access by the tracking UI. Historical paths are stored in Cassandra.

5. Handling Flash Sales and Peak Hours (Lunch/Dinner)

Traffic spikes during meal times are massive.

• Adaptive Throttling: If a restaurant is overwhelmed, the system automatically increases their "Estimated Prep Time" or hides them from the search results to prevent a bad user experience.
• Batching: To improve efficiency, the system may assign two orders from the same restaurant to a single courier if the destinations are close.

6. Menu Management and Search

• Search: Use Elasticsearch to handle fuzzy search ("Burgir" -> "Burger") and filtering by category/rating.
• Cache: Restaurant menus are cached in Redis with a short TTL, as they don't change every second but need to be retrieved millions of times.

Summary

The engineering of food delivery is a logistical dance. By treating the order as a strict state machine and using geospatial indexing for courier dispatching, you can build a system that scales to millions of orders across thousands of cities.

Engineering Standard: The "Staff" Perspective

In high-throughput distributed systems, the code we write is often the easiest part. The difficulty lies in how that code interacts with other components in the stack.

1. Data Integrity and The "P" in CAP

Whenever you are dealing with state (Databases, Caches, or In-memory stores), you must account for Network Partitions. In a standard Java microservice, we often choose Availability (AP) by using Eventual Consistency patterns. However, for financial ledgers, we must enforce Strong Consistency (CP), which usually involves distributed locks (Redis Redlock or Zookeeper) or a strictly linearizable sequence.

2. The Observability Pillar

Writing logic without observability is like flying a plane without a dashboard. Every production service must implement:

• Tracing (OpenTelemetry): Track a single request across 50 microservices.
• Metrics (Prometheus): Monitor Heap usage, Thread saturation, and P99 latencies.
• Structured Logging (ELK/Splunk): Never log raw strings; use JSON so you can query logs like a database.

3. Production Incident Prevention

To survive a 3:00 AM incident, we use:

• Circuit Breakers: Stop the bleeding if a downstream service is down.
• Bulkheads: Isolate thread pools so one failing endpoint doesn't crash the entire app.
• Retries with Exponential Backoff: Avoid the "Thundering Herd" problem when a service comes back online.

Critical Interview Nuance

When an interviewer asks you about this topic, don't just explain the code. Explain the Trade-offs. A Staff Engineer is someone who knows that every architectural decision is a choice between two "bad" outcomes. You are picking the one that aligns with the business goal.

Performance Checklist for High-Load Systems:

1. Minimize Object Creation: Use primitive arrays and reusable buffers.
2. Batching: Group 1,000 small writes into 1 large batch to save I/O cycles.
3. Async Processing: If the user doesn't need the result immediately, move it to a Message Queue (Kafka/SQS).

Advanced Architectural Blueprint: The Staff Perspective

In modern high-scale engineering, the primary differentiator between a Senior and a Staff Engineer is the ability to see beyond the local code and understand the Global System Impact. This section provides the exhaustive architectural context required to operate this component at a "MANG" (Meta, Amazon, Netflix, Google) scale.

1. High-Availability and Disaster Recovery (DR)

Every component in a production system must be designed for failure. If this component resides in a single availability zone, it is a liability.

• Multi-Region Active-Active: To achieve "Five Nines" (99.999%) availability, we replicate state across geographical regions using asynchronous replication or global consensus (Paxos/Raft).
• Chaos Engineering: We regularly inject "latency spikes" and "node kills" using tools like Chaos Mesh to ensure the system gracefully degrades without a total outage.

2. The Data Integrity Pillar (Consistency Models)

When managing state, we must choose our position on the CAP theorem spectrum.

3. Observability and "Day 2" Operations

Writing the code is only 10% of the lifecycle. The remaining 90% is spent monitoring and maintaining it.

• Tracing (OpenTelemetry): We use distributed tracing to map the request flow. This is critical when a P99 latency spike occurs in a mesh of 100+ microservices.
• Structured Logging: We avoid unstructured text. Every log line is a JSON object containing correlationId, tenantId, and latencyMs.
• Custom Metrics: We export business-level metrics (e.g., "Orders processed per second") to Prometheus to set up intelligent alerting with PagerDuty.

4. Production Readiness Checklist for Staff Engineers

• Capacity Planning: Have we performed load testing to find the "Breaking Point" of the service?
• Security Hardening: Is all communication encrypted using mTLS (Mutual TLS)?
• Backpressure Propagation: Does the service correctly return HTTP 429 or 503 when its internal thread pools are saturated?
• Idempotency: Can the same request be retried 10 times without side effects? (Critical for Payment systems).

Critical Interview Reflection

When an interviewer asks "How would you improve this?", they are looking for your ability to identify Bottlenecks. Focus on the network I/O, the database locking strategy, or the memory allocation patterns of the JVM. Explain the trade-offs between "Throughput" and "Latency." A Staff Engineer knows that you can never have both at their theoretical maximums.

Optimization Summary:

1. Reduce Context Switching: Use non-blocking I/O (Netty/Project Loom).
2. Minimize GC Pressure: Prefer primitive specialized collections over standard Generics.
3. Data Sharding: Use Consistent Hashing to avoid "Hot Shards."

Technical Trade-offs: Messaging Systems

Key Takeaways

• Order Management: Taking orders and managing the lifecycle (Created -> Accepted -> Prepared -> Picked Up -> Delivered).
• Inventory/Menu: Restaurants updating their menus and stock in real-time.
• Courier Dispatching: Efficiently matching an order with the best courier.

Read Next

• Consistent Hashing: The Secret Sauce of Distributed Scalability
• System Design: Designing a Video Conferencing System (Zoom / MS Teams)
• Building Production Observability with OpenTelemetry and Grafana Stack

Verbal Interview Script

Interviewer: "How would you ensure high availability and fault tolerance for this specific architecture?"

Candidate: "To achieve 'Five Nines' (99.999%) availability, we must eliminate all Single Points of Failure (SPOF). I would deploy the API Gateway and stateless microservices across multiple Availability Zones (AZs) behind an active-active load balancer. For the data layer, I would use asynchronous replication to a read-replica in a different region for disaster recovery. Furthermore, it's not enough to just deploy redundantly; we must protect the system from cascading failures. I would implement strict timeouts, retry mechanisms with exponential backoff and jitter, and Circuit Breakers (using a library like Resilience4j) on all synchronous network calls between microservices."