This question is locked. New answers and comments are not allowed.
We're looking to develop a SaaS app which operates in a multi-tenancy fashion.
Core tables would be centralised, whereas customer-specific information would be siloed into into it's own space, with its own username and password. We were thinking to put different tenants into different schemas, with a central master database to make database management somewhat simpler
We're wondering if there are any specific guidelines on the best way to achieve this using ORM?
Core tables would be centralised, whereas customer-specific information would be siloed into into it's own space, with its own username and password. We were thinking to put different tenants into different schemas, with a central master database to make database management somewhat simpler
We're wondering if there are any specific guidelines on the best way to achieve this using ORM?
1 Answer, 1 is accepted
0
Hi Praveen,
Petar
the Telerik team
We do not have built-in multi-tenant support inside of the product. The closest you can do is manage a different data context for each database used (using a different connection string). In memory you will have Database instanced for each database, that can be achieved by just using different connection strings (I assume the DB name can be the only thing that can change). I think the connection string usage can be hidden behind a front-end that authenticates the user.
Unfortunately at the moment we do not provide a tutorial or best practices articles on the subject but we can definitely look into adding this in the future.
Petar
the Telerik team
Follow @OpenAccessORM Twitter channel to be the first one to get the latest updates on new releases, tips and tricks and sneak peeks at our product labs!