diff --git a/qdrant-landing/content/articles/what-is-a-vector-database-revamp.md b/qdrant-landing/content/articles/what-is-a-vector-database-revamp.md index c71565b82..409b2d1af 100644 --- a/qdrant-landing/content/articles/what-is-a-vector-database-revamp.md +++ b/qdrant-landing/content/articles/what-is-a-vector-database-revamp.md @@ -406,7 +406,7 @@ Sharding efficiently distributes data across nodes, while replication guarantees **Multitenancy** allows you to keep data for different tenants (users, clients, or organizations) isolated within a single cluster. Instead of creating separate collections for `Tenant 1` and `Tenant 2`, you store their data in the same collection but tag each vector with a `group_id` to identify which tenant it belongs to. -Multitenancy dividing data between 2 tenants +Multitenancy dividing data between 2 tenants In the backend, Qdrant can store `Tenant 1`’s data in Shard 1 located in Canada (perhaps for compliance reasons like GDPR), while `Tenant 2`’s data is stored in Shard 2 located in Germany. The data will be physically separated but still within the same infrastructure. diff --git a/qdrant-landing/static/articles_data/what-is-a-vector-database-revamp/multitenancy-1.png b/qdrant-landing/static/articles_data/what-is-a-vector-database-revamp/multitenancy-1.png new file mode 100644 index 000000000..b87ea23e0 Binary files /dev/null and b/qdrant-landing/static/articles_data/what-is-a-vector-database-revamp/multitenancy-1.png differ diff --git a/qdrant-landing/static/articles_data/what-is-a-vector-database-revamp/multitenancy.png b/qdrant-landing/static/articles_data/what-is-a-vector-database-revamp/multitenancy.png deleted file mode 100644 index c45fb5dd6..000000000 Binary files a/qdrant-landing/static/articles_data/what-is-a-vector-database-revamp/multitenancy.png and /dev/null differ