News for hackers. Stuff that matters.

A comment on How Algolia Built Their Realtime Search as a Service. Parent comment

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.

[ Parent | on HN ]
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.

[ Parent | on HN ]