From a7763a8ecacec021995950196ae8496aa7c124ad Mon Sep 17 00:00:00 2001 From: Ebicoglu Date: Sat, 31 Aug 2024 20:41:33 +0300 Subject: [PATCH] Update Post.md --- .../2024-08-30-Do-You-Need-MultiTenancy/Post.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/Community-Articles/2024-08-30-Do-You-Need-MultiTenancy/Post.md b/docs/en/Community-Articles/2024-08-30-Do-You-Need-MultiTenancy/Post.md index d5c65db1aa..068b8bc4cd 100644 --- a/docs/en/Community-Articles/2024-08-30-Do-You-Need-MultiTenancy/Post.md +++ b/docs/en/Community-Articles/2024-08-30-Do-You-Need-MultiTenancy/Post.md @@ -1,4 +1,4 @@ -# Do You Need Multi-tenancy? +# Do You Really Need Multi-tenancy? This article discusses whether you need a multi-tenancy architecture for your next project. Answer my critical questions to decide if multi-tenancy suits your application or not! @@ -19,7 +19,7 @@ It’s an architectural approach to building SaaS solutions. In this model, the -## Multi-tenant Application Development is Hard! +## Multi-tenant Application Development is Hard - Reconsider! **Developing a multi-tenant application is harder** compared to non-multi-tenant applications. You add `TenandId` to all your shared entities. And each time you make a query, you need to filter by `TenantId`. There is an increased risk of security breaches if one tenant's data is compromised. Multi-tenancy can limit the extent of customization available to each tenant since they all operate on the same core infrastructure. Also, in a microservice environment, things get two times more complicated. So you should carefully consider if you need multi-tenancy or not. Sometimes, I got questions like;