#community-help

Transitioning from Elasticsearch to Typesense

TLDR Martin inquired if Typesense can replace Elasticsearch. Kishore Nallan clarified Typesense has a different focus and will not fit all Elasticsearch use cases.

Powered by Struct AI
6
29mo
Solved
Join the chat
Jul 09, 2021 (29 months ago)
Martin
Photo of md5-4c44d17869045701f2ca4035972ad4c5
Martin
12:07 PM
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?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
12:08 PM
👋 When you mean by drop-in replacement, do you mean using the same Elastic API and clients?
Martin
Photo of md5-4c44d17869045701f2ca4035972ad4c5
Martin
12:11 PM
Yes, mainly a compatible REST API that works with the existing Elasticsearch clients.
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
12:12 PM
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.
Martin
Photo of md5-4c44d17869045701f2ca4035972ad4c5
Martin
02:26 PM
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.
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
03:20 PM
Okay, will be happy to help as you build it out.