Latency Budget
The response-time allocation for each supplier or service in an end-to-end search. Timeouts and progressive results should be designed around it.
Why it matters
Metasearch fan-out architectures need resilience because upstream latency and data volatility are unavoidable. Cache, timeout and retry decisions affect not only backend performance but also whether the displayed offer is trustworthy. These concepts should be designed with SLOs, freshness and failure isolation.
What does it look like in practice?
When one supplier's p95 latency rises, timeout, circuit breaker and fallback cache may work together. A successful stale fallback can still increase price-quality risk.
Implementation questions
- What is the end-to-end latency budget?
- Are cache age and source timestamps retained?
- Which error classes are retried?
- Can one provider failure degrade every supplier?
Common mistakes
- Retrying every error class
- Optimizing cache hit ratio without freshness
- Allowing one provider to block the entire fan-out
Where does it appear in the travel stack?
Latency Budget commonly appears across resilience layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Search Fan-Out & Partial Results Architecture
Manage parallel travel-provider calls with latency budgets, bounded concurrency, early useful results and controlled final merging.
Explore →Supplier Latency and Timeout Budgets in Metasearch
Design timeout budgets, parallel supplier calls, partial-result handling, circuit breakers and latency SLOs for hotel and flight metasearch search pipelines.
Explore →Provider Partial Outage / Degraded Mode Troubleshooting
Diagnose travel-provider partial outages where latency, timeouts or specific capabilities degrade without a total service failure.
Explore →Sync vs Async Travel Booking Architecture
Compare synchronous and asynchronous travel booking orchestration across latency, recovery, UX and provider capabilities.
Explore →ARI vs Live Search vs Reprice: Hotel Pricing and Availability Lifecycle
Compare ARI, live search and reprice/check flows across freshness, granularity, latency, booking confidence and source-of-truth.
Explore →MetaSearch Benchmark Methodology: API Latency and Reliability
Methodology for travel API benchmarks covering latency, timeouts, error rate, cache state, geography, sample size and reproducibility.
Explore →