Multi-Supplier Hotel Search Architecture

Multi-supplier hotel search is not simply sending the same request in parallel. The real problem is converting different identity, rate, latency and failure contracts into one traveler-facing search contract.

Production scenario

One hotel/date/occupancy search fans out to three suppliers and one direct channel. Some providers return in 300 ms, others in 2 seconds; the same property has different IDs and tax/fee semantics.

Architecture flow

Multi-supplier hotel search flow

Mermaid source (.mmd)

Key entities

Use explicit SearchContext, CanonicalProperty, SupplierPropertyRef, RawOffer, NormalizedOffer, OfferFingerprint, ProviderHealth and SearchExecution models.

Do not expose supplier DTOs directly to the UI.

Design decisions

Calling every supplier maximizes coverage but increases latency and cost. Eligibility should consider market, coverage, quota and provider health.

Normalization should create a common model while preserving source IDs and raw context for later repricing and debugging.

Concurrency and latency budget

Assign provider-specific timeouts inside an overall search budget. If the SLA is 2 seconds, waiting 2 seconds independently for every provider is not a useful budget.

Reserve time for final merge and ranking.

Failure modes

Typical failures include one slow supplier blocking the whole search, duplicate properties, stale rates, tax mismatches, retry amplification and incomplete ranking sets.

Partial results

Returning useful early results can be better than waiting for every provider. The product and analytics layers must distinguish partial from final state.

Observability

Track supplier success rate, latency percentiles, offers per supplier, property-mapping coverage, duplicate rate, partial responses, price mismatches and total search latency.

Alternatives

For low volume with one or two predictable suppliers, simple synchronous orchestration can be enough. More suppliers and variable latency justify bounded fan-out, bulkheads and circuit breakers.

Production checklist

Define supplier-specific timeouts, bounded concurrency, canonical search context, mapping, offer fingerprints, raw-response traceability, partial-result semantics, health-aware eligibility and provider-level metrics.