
Programming & Tech • Posted 2 months ago
Three hotel suppliers, three different APIs, three different ideas of what availability means. Our booking flow currently supports one. We want an adapter layer with a single internal interface, sensible caching, and graceful degradation — if one supplier is slow we show the others rather than hanging the page. The interesting problems here are timeouts, partial failures and reconciling inventory that disagrees. Please address those in your proposal; the happy path is the easy part.