RAG and search
How we selected the next vector database at Booking.com
Our short summary of Booking.com’s engineering write-up. The full story, with all the detail, is on their blog.
Read the full write-up on booking.ai (opens in a new tab)Problem
Teams needed a fast, scalable vector store that could handle many use cases and high traffic.
Solution
They built a shared vector‑search infrastructure, evaluated different databases, and chose a new system that supports hybrid search, large capacity, and high request rates.
Want the architecture, code and numbers? They’re in the original post.
Read the full write-up on booking.ai (opens in a new tab)
HubSpot
Elastic