Understanding on Multi-tenancy

Support
2

hi @adithya.ch !

As long as your teams doesn’t use the same collection name, they can use the same cluster.

  1. On that case, all teams will have access to all collections. There is a feature request for Role Based Access Control, RBAC, that is in the roadmap
  2. Suppose your collection will be used for different customers, or users. You can create one tenant per customer. That way each tenant will have isolation from each other on that specific collection.

Before tenants, Weaviate developers used to create all objects in the same collection, having a property to differentiate each customers using a filter.

This was far from optimal. Not only because the data was not isolated, but also because removing a tenant triggered unnecessary change in the vector index.

Using tenants, you can remove, disable (status:COLD) or enable (status:HOT) a tenant when necessary. For example, when a user logs in, you can make it HOT, saving considerable on memory usage.

  1. There isn’t for now, Sorry :frowning: This is what RBAC should deliver when the time comes.

Please, consider giving your :+1: on RBAC feat request so we can better track/measure what should be planned for next releases.

Thanks!