daibo

So my guess would be you have both a inverted index and some sort of ANN index deployed, and route queries to those depending on the inferred intent? Could be at least 1 order of magnitude faster though.

Nothing wrong with that though

There are just the two of you working on typesense right? Surely having some more people working on the core product (up to five?) should help, no? I'm also building an Algolia alternative, with three engineers including me working on the core engine, and sometimes I wish I had one or two more.

This really resonates with me, I'm currently bootstrapping an Algolia alternative too, albeit with the Saas business model instead of open core. All the best!

I run a Search as a Service startup, would like to sponsor your doc search. Shoot me an email or dm me on twitter @linh_at_anvere

Meilisearch is rather the free and open alternative to Algolia, as it focuses on solving zero-config and easy to deploy autocomplete search, as opposed to analytics at scale.

Did the elasticsearch vs aws fiasco affect your ability to raise, considering it highlighted the risks of the opencore business model?

Hey, send me an email to linh at anvere.net. Or twitter dm @linh_at_anvere edit: anvere is a Search as a Service that I am currently building

Are you using Opensearch for logging or site search? $371 seems like a lot for a low traffic site. You can probably reduce the cost to a fraction by doing some research on alternatives

Not really a side project, but I haven't quit my job for it so..

I'm building a Search as a Service like Algolia. Currently earning $700 a month from an early customer. Anvere.net

Yes doclist compression is a must. Higher intersection throughput and less bandwidth stress. Are you loading your doclists from persistent storage? What is your current max rps?

What's the size of your index in records?

Yes sure. Send me and email to linh at anve.re

I made an Algolia alternative, https://anvere.net, launching soon. Currently earning $700 from an early adopting customer.

The search engine under the hood was built in Rust, for a search as a service that we plan to launch soon.

Thanks :)

It's powered by a search engine that we are building from scratch

I am combining symmetric deletes with a trie for fuzzy autocompletion and it is working pretty well.

I assume you are using Symspell for fuzzy search and prioritize candidate frequency over edit distance. My input "algolai" returns results for "angola" even though "algolia" was just 1 transposition away. Anyway just dropping in to say that stuff on your github helped me figure out a lot while building a search engine from scratch. Good luck with SeekStorm!