Industry
Travel software.
Travel booking is distributed transaction management against suppliers you do not control, over inventory that expires. A seat unsold at departure is worth nothing, and the price you quoted a second ago may no longer exist.
What shapes the architecture
Constraints that are specific to this sector.
These are the things that would be wrong or meaningless if written about a different industry. They are design inputs, not compliance paperwork added at the end.
- 01
Search and book use different sources of truth
Cached availability makes search fast; only the supplier can confirm a booking. Price and availability must be revalidated at booking, and the UI has to handle the change gracefully rather than failing.
- 02
Booking is a distributed transaction with no rollback
Flight confirmed, hotel failed, payment captured. There is no two-phase commit across suppliers, so compensating actions and a reconciliation queue are mandatory design elements.
- 03
GDS and NDC are different worlds
Legacy GDS semantics and airline NDC offers model fares and ancillaries incompatibly. Normalising both into one internal offer model is the core of the domain.
- 04
Cancellation rules are the real complexity
Fare rules, partial refunds, date changes and supplier penalties vary per booking. Encoding them as data attached to the booking beats reimplementing them per supplier.
Typical work in travel.
- Flight and hotel booking engines
- Multi-supplier inventory aggregation
- Dynamic packaging and bundling
- Itinerary and trip management
- Cancellation and refund workflows
- Agent and corporate booking portals
What it has to talk to.
- GDS (Amadeus / Sabre)
- IATA NDC
- Payment gateways
- Channel managers
- Airline APIs
Integration surfaces are where most sector projects actually fail. We treat each one as a boundary with its own translation layer, rather than letting an external format leak into the domain model.
Other sectors
Explore the rest.
Start here
Tell us the problem.
We'll be honest about the fit.
A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.
- Reply within 24 hours
- No sales sequence