
✈️ Travel & Hospitality · Deployment · Pro
How an online travel aggregator is deployed to handle search spikes: search fan-out to suppliers, caching, and separate booking services.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Deployment for an online travel aggregator on Kubernetes: users hit a CDN and API gateway; the search service fans out requests to supplier connectors (GDS, airline NDC APIs, hotel bed banks) and caches results in Redis for a few minutes. Booking and payment services run in a separate node pool with their own database. Kafka carries booking events to notifications and analytics.
flowchart TB
U[Users] --> CDN[CDN]
CDN --> GW[API Gateway]
subgraph K8s[Kubernetes Cluster]
subgraph SearchPool[Search node pool - autoscaling]
SS[Search Service]
SC[Supplier Connectors]
end
subgraph BookPool[Booking node pool]
BS[Booking Service]
PS[Payment Service]
end
NOTI[Notification Service]
end
REDIS[(Redis Fare Cache)]
PG[(Bookings DB)]
KAFKA[Kafka]
SUP[GDS, airline NDC, hotel bed banks]
GW --> SS
SS --> REDIS
SS --> SC --> SUP
GW --> BS
BS --> PS
BS --> PG
BS --> KAFKA --> NOTIHow an online travel site books a flight: fare search across airlines, seat hold, passenger details, payment and ticket issue.
Every state of a hotel reservation from enquiry to checkout, including pay-at-hotel, cancellations and no-shows.
A hotel chain's reservation platform: booking engine, property management system, channel manager for OTAs and revenue management.
A database schema for an airline or hotel loyalty programme: members, tiers, earning and burning points, partners and rewards.
How a passenger checks in for a flight: online or at the airport, seat selection, documents check, bags and boarding pass.
Mobile check-in for a hotel: ID upload, room assignment by the PMS, payment hold and a digital room key.