krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-06 19:38:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update qdrant-landing/content/documentation/guides/multitenancy.md

Browse Source 
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
This commit is contained in:
Andrey Vasnetsov
2025-11-17 10:29:22 +01:00
committed by GitHub
co-authored by Abdon Pijpelink
parent 8d1b7d8003
commit 1da68024ff
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/guides/multitenancy.md
+1 -1
View File
@@ -69,7 +69,7 @@ One downside to this approach is that global requests (without the `group_id` fi
## Tiered multitenancy ## Tiered multitenancy
In some real-world applications, tenants might not be equally distributed. For example, a SaaS application might have a few large customers and many small ones. In some real-world applications, tenants might not be equally distributed. For example, a SaaS application might have a few large customers and many small ones.
Large tenancts might require extended resources and isolation, while small tenants should not create too much overhead. Large tenants might require extended resources and isolation, while small tenants should not create too much overhead.
One solution to this problem might be to introduce application-level logic to separate tenants into different collections based on their size or resource requirements. One solution to this problem might be to introduce application-level logic to separate tenants into different collections based on their size or resource requirements.
There is, however, a downside to this approach: we might not know in advance which tenants will be large and which stay small. There is, however, a downside to this approach: we might not know in advance which tenants will be large and which stay small.