FoodDash — Food Delivery Platform

## Executive Summary **Project:** FoodDash — multi-restaurant food delivery platform **Architecture Style:** Microservices with API Gateway **Primary Stack:** TypeScript / Next.js / React Native / Node.js / PostgreSQL / Redis ### User Roles - **Customer** — browse restaurants, place orders, track delivery in real-time - **Restaurant Owner** — manage menu, accept orders, view analytics & payouts - **Delivery Driver** — accept deliveries, navigate to pickup/drop-off, track earnings - **Platform Admin** — onboard restaurants, resolve disputes, manage promotions ### Key Decisions 1. **5 client applications** — Customer Web (Next.js), Customer Mobile (React Native), Restaurant Dashboard (React), Driver Mobile (React Native), Admin Panel (React) 2. **8 backend microservices** — API Gateway, User Service, Restaurant Service, Order Service, Payment Service, Delivery Service, Notification Worker, Analytics Worker 3. **Service-per-database** — each core service owns its own PostgreSQL database for data isolation 4. **Real-time order tracking** — WebSocket connection from Delivery Service to customer apps with live driver location 5. **Event-driven notifications** — Order and delivery status changes fire events to a message queue consumed by the Notification Worker ### Risks & Mitigations | Risk | Likelihood | Mitigation | |---|---|---| | Driver matching latency during peak hours | High | Geospatial indexing + pre-computed delivery zones | | Payment split complexity (platform + restaurant + driver) | Medium | Stripe Connect with automatic payout scheduling | | Real-time location battery drain on driver app | Medium | Adaptive polling frequency based on delivery state |