From 324644dbf29d8f136454c2ec7a9322d03cce1408 Mon Sep 17 00:00:00 2001 From: Ebicoglu Date: Mon, 2 Sep 2024 14:37:08 +0300 Subject: [PATCH] grammar fix --- .../2024-09-01-Do-You-Need-MultiTenancy/Post.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md b/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md index fb49f40b2f..6926c5a604 100644 --- a/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md +++ b/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md @@ -46,7 +46,7 @@ Ask yourself the following questions if you cannot decide whether your app needs 1. Can a user be shared among other tenants? 2. Any tenant needs to see other tenant's data? -3. Does your application still work if you physically move one of the tenants physically? +3. Does your application break when you physically move one of the tenants?? 4. Do your customers need higher security and better GDPR enforcement? 5. Do you need cumulative queries over your tenants? @@ -72,9 +72,9 @@ On the other hand, if you serve several online shopping websites dedicated to di -##### **3. Does your application still work if you physically move one of the tenants physically?** +##### **3. Does your application break when you physically move one of the tenants?** -If your answer is **YES**, you should **stop making it multi-tenant**. This means your tenants are tightly coupled with the application's infrastructure or database, and this requirement prevents you from making it multi-tenant because it disrupts the entire system when you take out a tenant. +If your answer is **YES**, you should **stop making it multi-tenant**. It is **not a multi-tenant app**! This means your tenants are tightly coupled with the application's infrastructure or database, and this requirement prevents you from making it multi-tenant because it disrupts the entire system when you take out a tenant. @@ -99,11 +99,11 @@ Do you need cumulative queries over your tenants? If your answer is YES, then yo ## Conclusion -- It's important to decide on the first day whether your application needs to be multi-tenant! To decide this, consider these topics; +- It's important to decide on the first day whether your application needs to be multi-tenant. To decide this, consider these topics; - **Do my tenants really have a relationship with each other?** No, they have nothing to do in common; **OK, go with multi-tenancy**. - - **My tenants don't have a relationship** with each other, and the only thing they have in common is sharing my application. **If yes, go with multi-tenancy**. - - If **a tenant leaves the system, will the other tenants be affected** when I remove its data from the system? **If others are not affected, go with multi-tenancy**. + - **My tenants don't have a relationship** with each other, and the only thing they have in common is sharing my application. **OK, go with multi-tenancy**. + - **When a tenant leaves the system (by removing their data), the other tenants also stop working** This means that the tenants are coupled. **Do not do multi-tenancy!**