Technical design for a platform with real time ordering system can be demonstrated with several layers as below with certain assumptions and considering the end to end technical design can be show as below:

Let’s have some brief description for different layers and components:
Frontend – Mobile & Web Dashboards
Platform user interfaces for the end users which includes driver android app, dashboards and other internal reporting and analytics dashboards are needed with the platform as presentation layer.
CDN & WAF
For latency, reliability and traffic spikes will be managed by putting the critical servers behind the CDN layer. Also, WAF policies will be enabled to secure the APIs and infrastructure.
Primary Environment
The active environment will always available, and all the application requests will be served via the primary environment.
Disaster Recovery or Secondary Environment – active/passive
For the disaster recovery strategy we can plan to use active/passive or active/active based on the pre-defined RTO and RPO where all the critical resources will be backed-up to different region with replications and synced data.
API Gateway
Azure API Management will helps in meeting the challenges like abstract backend architecture diversity and complexity from API consumers, Securely expose services hosted, protect, accelerate and observe APIs.
Microservices
The microservices will be separated based on the requirements and usage to route the requests to the respective APIs.
Database and Storage
The database and storage should be designed based on the requirements and in three secured and 99.999% response availability for the requests made for the data.
Event Streaming Platform
For event streaming and real time data ingestion Kafka will be used which has further exposed in the next upcoming slides.
Databases and Libs
The master and centralized data which might be available inside the databases and can be ingested inside the system by pre-processing and push with real time streaming as producer and consumer streams.
External and Third Party Systems
This is the future external and third-party system integration layer which is available to fetch data from any type of system and execute withing the platform.