I had a question regarding the number of collections in Weaviate. Is there a limit or bottleneck on the number of collections you should have?
Hi @tstra !
There isn’t any known limitation other than hardware, AFAIK.
Of course, having millions of collections, for example, can add up to the re|start up time of a node in your cluster. There are some mitigations for that, like lazy shard loading that will prioritize if a shard is requested and not yet loaded.
Not sure if it applies to your use case, but it is interesting to learn about multi tenancy. The approach of having multiple users/tenants per one collection is way better than having one collection per user for your app.
The worst solution is having multiple users data indexed on a single collection and filtering it out by one property.
Let me know if this helps