At first I thought that a tenant would be a new DB here I could separate the data from different clients(I know that this is adding a physical shard), but I found that in a class(or index) I can have multiple tenants what is the advantage then if the tenant is used to share multiple indexes instead of isolate them?
Each tenant will have it’s own index, and isolated physical shard.
This is specially helpful when you want to delete a tenant entirely or just put it on COLD state (saving resources).
Also, crud operations on one tenant will not affect the other ones.
Our CTO gave a really nice talk about this subject:
Let me know if that helps
Thank you, yes it did help!