---
title: "Design: ride matching"
description: "Design ride matching: search for candidate drivers, record an offer, accept it once, handle deadlines and cancellations, and grow without two owners."
canonical_url: "https://fanout.sh/system/archive/ride-matching-system-design"
md_url: "https://fanout.sh/system/archive/ride-matching-system-design.md"
last_updated: "2026-11-11"
access: "pro-preview"
---

# Design: ride matching

Design ride matching: search for candidate drivers, record an offer, accept it once, handle deadlines and cancellations, and grow without two owners.

- Access: Fanout Pro (public preview)

## The core idea

A ride-matching service takes a pickup request, finds eligible drivers, and turns a driver's acceptance into an assignment.

The map helps choose whom to ask.

## In this lesson

- What the service must promise
- Candidate search and assignment have different jobs
- Choosing the closest driver is a policy
- Recording an offer
- Accepting an offer once
- Deadlines, movement and cancellation
- Delivering the decision to the apps
- The executable API and its boundaries
- Growing without creating two owners
- Run the race and recovery

## Continue reading

Pro unlocks video lessons, visual walkthroughs, full notes, diagrams, case studies, and implementations across the System Design archive.

---
This representation contains public Fanout content only. Protected Pro lessons, account data, billing, checkout, and pricing are not included.

Browse the public content map: https://fanout.sh/sitemap.md
