@llabball The search is powered by the Algolia search engine, a hosted search engine. Under the hood, it's C++ code hosted in an NGinx module. The small JS code snippet that we provide you calls the Algolia API at each keystroke, to retrieve the most relevant results. You can read about it here: http://stackshare.io/posts/how-a... or https://www.algolia.com/product
@sylvainutard Ah ok, a server-side search. Every keystroke means you expecting to being able to handle a lot of requests in-time. Can you crunch some numbers with us? What's your capacity in terms of concurrency, avg response time ...
@llabball Oh yes, that's a bunch of API calls a month :) Last month we processed ~8B queries out of a total of ~30B operations done on our API. On average, search queries are processed in <15ms and with our Distributed Search Network (https://www.algolia.com/dsn) we're confident about spending <60ms on the network wherever you're on the planet: realtime search \o/ Some of our customers have 1 big index with up to hundreds of millions of objects; other have up to thousands of small indices, it scales pretty well :)
For DocSearch, we've set up an Algolia account replicated in 10 regions around the world to provide the best search experience to all your end-users.
Hey hunters,
As the year winds down, the team at Algolia would like to help you celebrate with our 2015 holiday gift: DocSearch.
With DocSearch, we’re making it easier to search within your documentation, and we’re doing it for free. As in, you just fill out the form, and we send you the code to implement DocSearch within your documentation. You don’t need to create an account or send us any money!
Check out some existing implementations like http://eslint.org/ and http://docs.scala-lang.org/ and let us know if you’d like DocSearch for your own documentation :)
Happy Holidays!
Replies
Algolia
Algolia
Algolia
AdInboxMe
Thank you for this tool
Pros:Amazing, fast and easy to set up
Cons:Nothing