PracHub
QuestionsPremiumLearningGuidesInterview PrepCoaches
|Home/System Design/Axon

Design an airline booking system

Last updated: May 29, 2026

Quick Overview

This question evaluates a candidate's ability to design scalable, consistent, and resilient distributed systems for transactional domains, emphasizing API design, data modeling, concurrency control, idempotency, seat inventory guarantees, and external integrations like payments and ticketing.

  • hard
  • Axon
  • System Design
  • Software Engineer

Design an airline booking system

Company: Axon

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Technical Screen

Design an airline booking system that supports flight search (including multi‑leg connections), booking, seat selection, and itinerary modification/cancellation. Define core REST/gRPC APIs for search, book, modify, and cancel; the data model for flights, legs, fares, seat inventory, reservations, and users; and how to ensure seat availability, atomicity across connecting segments, and idempotency. Discuss consistency guarantees, concurrency control to prevent overbooking, and strategies for strong vs. eventual consistency across regions. Explain integration with payment, ticketing, notifications, and refund flows. Address indexing and caching for search queries (origins, destinations, dates, cabin), pagination and sorting, and flexible‑date search. Cover scaling, sharding, and read/write patterns; resiliency (failover, retries, sagas), observability, and SLAs. Compare trade‑offs for single‑airline vs. multi‑tenant OTA scenarios and outline partner API integration and rate limiting.

Quick Answer: This question evaluates a candidate's ability to design scalable, consistent, and resilient distributed systems for transactional domains, emphasizing API design, data modeling, concurrency control, idempotency, seat inventory guarantees, and external integrations like payments and ticketing.

Related Interview Questions

  • Design fulfillment truck routing and inventory system - Axon (medium)
  • Design camera-footage upload with custody chain - Axon (medium)
  • Design device logging system with offline upload - Axon (medium)
  • Design an image-to-multilanguage translator - Axon (medium)
  • Design a Test Orchestration System - Axon (medium)
Axon logo
Axon
Aug 7, 2025, 12:00 AM
Software Engineer
Technical Screen
System Design
35
0

System Design: Airline Booking System

You are designing an airline booking platform that supports searching, booking, seat selection, and itinerary modification/cancellation. Assume consumer traffic is global, search is read-heavy, booking is write-critical, and seat inventory must not oversell.

Functional Scope

  • Flight search: one-way, round-trip, multi-leg connections (max 2 stops), cabin filters, passenger types.
  • Booking: create reservation, hold seats, payment, ticketing.
  • Seat selection: seat map retrieval and seat assignment per segment.
  • Modify/cancel: reprice and change flights, partial/whole cancellation, refunds.

APIs to Define

  • Core REST and gRPC for: search, price/offer retrieval, book/confirm, modify, cancel, seat selection, fare-calendar (flexible dates).
  • Idempotency handling for write operations.

Data Model to Specify

  • Flights, legs/segments, fare classes and rules, seat inventory (by fare bucket and cabin), offers, reservations/PNR, tickets, payments, users, refunds.

Guarantees and Controls

  • Ensuring seat availability and atomicity across connecting segments.
  • Idempotency of booking/modify/cancel.
  • Consistency guarantees (strong vs eventual) and concurrency control to prevent overbooking.
  • Multi-region strategy: strong vs eventual consistency across regions.

Integrations

  • Payments (authorize/capture/void/refund), ticketing issuance, notifications.

Search and Performance

  • Indexing and caching for queries by origin, destination, dates, cabin; pagination, sorting; flexible-date search.

Scale and Resilience

  • Scaling, sharding, read/write patterns.
  • Resiliency: failover, retries, sagas/compensations.
  • Observability and SLAs.

Multi-Tenancy and Partners

  • Trade-offs: single-airline vs multi-tenant OTA scenarios.
  • Partner API integration and rate limiting.

Deliver a coherent design covering the above, including minimal assumptions needed to make the system concrete.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Axon•More Software Engineer•Axon Software Engineer•Axon System Design•Software Engineer System Design
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.