Sorry if that has been asked before, but are there any considerations to build out Typesense as an Elasticsearch drop in replacement, making it easier to transition? Or is that too different an audience?

👋 When you mean by drop-in replacement, do you mean using the same Elastic API and clients?

Yes, mainly a compatible REST API that works with the existing Elasticsearch clients.

Mostly because we will then have to inherit all the bad parts 🙂 On a serious note, Elastic is a much bigger project with just way too many use cases. Typesense is hyper focussed in solving a subset of the use cases. For e.g. we don't recommend using Typesense for logs, metric etc. while you can throw the kitchen sink at Elasitc.

That makes sense. So then I have to think about addressing this for a specific open source project, which will become my focus of work in August.

Okay, will be happy to help as you build it out.