News for hackers. Stuff that matters.
Re:How Algolia Built Their Realtime Search as a Service by karterk on Wednesday May 02, 2018 @11:26PM (#16983140)
Shameless plug: if you are looking for a simple, fast, fuzzy search engine that you want to host yourself, take a look at Typesense: https://github.com/typesense/typesense
Re:How Algolia Built Their Realtime Search as a Service by Antrikshy on Thursday May 03, 2018 @01:58AM (#16983653)
Only tangentially related, but...

If you're looking for a front-end library for autocompletion, Twitter's typeahead.js is a nice one: https://github.com/twitter/typeahead.js

If you want one that works seamlessly with your React setup, React Autosuggest is pretty neat: https://github.com/moroshko/react-autosuggest

Re:How Algolia Built Their Realtime Search as a Service by vvoyer on Thursday May 03, 2018 @02:31AM (#16983802)
Careful though because typeahead.js is not maintained at all even if not said clearly on the GitHub repo
Re:How Algolia Built Their Realtime Search as a Service by rawoke083600 on Thursday May 03, 2018 @02:23AM (#16983767)
only more less related... if you need to access any of the search servers on the internet... take a look at www.fibretiger.co.za for your fibre pricing ! :P
Re:How Algolia Built Their Realtime Search as a Service by jazoom on Thursday May 03, 2018 @08:00AM (#16985127)
That looks good. According to your FAQ the main disadvantage this has compared to Elasticsearch is not being able to scale horizontally.

Have you considered using FoundationDB as a storage layer to match that feature?

Disclaimer: I have no idea how to build a distributed search engine.

Re:How Algolia Built Their Realtime Search as a Service by karterk on Thursday May 03, 2018 @09:01AM (#16985544)
I might not be 100% correct on this, but it seems like even Algolia keeps all records in a single host and uses the other 2 hosts for only high availability.

Having said that, exploring a FoundationDB integration is definitely an interesting idea. However, quite a lot of use cases can be served perfectly well with a simple master+slave set-up, so my primary focus is on that until there is enough demand for horizontal scalability. For e.g. Typesense is not a great fit for things like log data that typically need large amounts of storage.