From 8c2baf658b72644f6d295dfd3ca807ab13cc30e9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Halil=20=C4=B0brahim=20Kalkan?= Date: Sun, 27 Jul 2025 20:55:33 +0300 Subject: [PATCH] Update POST.md --- .../2025-07-26-Separate-Tenant-Schema/POST.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md index 9b8dd47521..0f473e9999 100644 --- a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md +++ b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md @@ -463,7 +463,16 @@ In brief, when you make changes on your entity classes; ## Conclusion +In this article, I covered two important aspects of multi-tenant application development: +* How ABP startup templates provide a multi-tenant application setup, so some tenants may store their data in a single (main, shared) database while some others may have their own dedicated database. +* Demonstrate how it can manage database migration process on the fly for multiple databases. + +I started by defining different database models for multi-tenant applications (Single database, separate databases, and hybrid), showed how to create an ABP application that supports hybrid model, explained the DbContext structure that is coming with the solution template, demonstrated how to define entities, create and apply database migrations in such an application. + +I hope this article gives you a good understanding the problem and the solution provided by the ABP Framework. Please write your questions or comments under this article. + +Enjoy coding! :) ## Further Reading