Is weaviate good for my use-case? Comparing with mongo

hi @peguerosdc !! Welcome to our community :hugs:

Of course my opinion will be biased :see_no_evil: towards Weaviate and I will be here cheering and ready to help you succeed with us :wink:

Some notes:

We are also committed to have a great JS/TS client.

It happens that within our community, Python is more popular language.

Right now, our new JS/TS client (v3) is in the oven, and should go for GA in the next couple weeks: GitHub - weaviate/typescript-client: Official Weaviate TypeScript Client

On that, we would love to hear what you think about it, and how we can improve this new client.

You can already see it’s new syntax in our documentation (JS/TS Beta). Also, if you want to help on it’s development, we have a #javascript channel in our public slack where you can have direct access to our dev team :wink:

Indeed, you cannot remove a property as of now. If you do want to change your schema down the road, you can migrate your data over to a new collection or cluster with the schema you want. This will be fairly easy and quick, considering you expect to not have millions of records.

We even have a guide for that

Anyway, let me know if you have any other questions, and I’ll be more than happy to help!

Ps: considering you plan on doing recommendation, have you seen this repo? It may help you: GitHub - weaviate/ref2vec-ecommerce-demo: Demo on using Weaviate's ref2vec vectorizer for building Recommendation Systems!

Thanks and again, welcome to our community :slight_smile:

1 Like