DoorDash's Composable Workflow Platform for Global Onboarding
DoorDash re-architected its Dasher onboarding system into a unified, composable workflow platform to support global expansion and reduce engineering complexity. This new architecture replaces a fragmented legacy system with a modular, step-based orchestration model, enabling consistent and localized onboarding experiences across various markets. The design emphasizes reusable modules, declarative workflows, and a unified status map for improved reliability and maintainability.
Read original on InfoQ ArchitectureDoorDash faced significant challenges with its legacy Dasher onboarding system as it expanded globally, leading to fragmented logic, multiple API versions, duplicated business logic, and tightly coupled dependencies. This made managing applicant progress difficult and increased operational risks. The solution was to re-architect the system into a unified, composable workflow platform designed for global scale.
Core Architectural Principles
- Composable Workflow Engine: The new system is built around a configurable workflow engine. This engine orchestrates reusable 'step modules' based on declarative workflow definitions. This allows country-specific variations to be expressed through configuration rather than hard-coded logic or code forks.
- Reusable Step Modules: Each module encapsulates its own business logic, including validation, vendor integrations, completion criteria, and failure handling. This promotes independent ownership and autonomous evolution of modules, adhering to shared interface contracts.
- Unified Status Map: A single source of truth for applicant progress, replacing disparate tables. Each module updates a standardized status entry (e.g., 'in progress', 'complete', 'skipped'). The workflow engine evaluates this map to determine the next actionable step, simplifying retry logic and enabling safe parallel execution.
Key Takeaway for System Design
Designing for global scale early, reasoning from first principles, and investing in reusable modules and clear data contracts are crucial for building a maintainable and scalable architecture. Prioritizing backward compatibility and defining module ownership are essential during phased migrations of complex systems.
Benefits and Future Enhancements
The phased migration to the new architecture, starting with the US and then rolling out to other countries like Australia and Canada, validated the system's portability. The composable nature of workflows and reusability of modules significantly reduced development effort for each new market. Future enhancements include dynamic workflow configuration, step versioning for staged rollouts, and operational tooling to manage regional variations without code deployments.