How i can handle Multi Tenancy In a big cloud based applicat

Mark Tabor

i want to build a big cloud based system which is SAAS based and multi tenant how do i identified that this users belongs to this agency like my agencies will subscribe for my services Like i would have plan , A,B,C then how do i control the users like this users belongs to this agency and this users belongs to this agency ?

5 Replies

Know the answer? Post it — somebody with the same question will find it here.

Chanakya Jayabalan8y ago
Accepted answer
Hi Mark,

I dont see a problem in using Angular as long as your API layer is secured enough.Even if there are versions of angular coming up, you can stop with current version as long as you are happy with the features it provides. Also there are not much differences when it comes to angular versions atleast in recent releases. You can also look at react whcih is gaining popularity for its virtual DOM & the logical seperatio of tiers. Ans yes you can even use angular with .NET core. So its up to you what goes in to client & server side code.

And you shoud really check at various options in securing azure api. Look for topics like Azure API Management, securing using AAD, CORS protection, SSL, IP based protection & more.
Mark Tabor7y ago
is there any demo application which i can follow to use like to seperate my TDO's and API I want to see the project structure build using web api and .NET MVC.
if anyone can share
Mark Tabor8y ago
Thanks Chanakya Jayabalan
Mark Tabor8y ago
Thanks Chanakya Jayabalan, I will use Azure app service, but still i am looking for the best architectuere like i have very secure data payment transaction involved , i have android app too , should i use angular but i am thinking google would role out new one for every next three month so it would take lot of maintenance, should i use .net core or mvc?
Chanakya Jayabalan8y ago
Hi Mark,

If you are building a multitenant app, then you can very well leverage Azure app service to implement it. And to make it a real SaaS, you would use custom domains & you spin out one tenant for each customer, Something like https://customer1.yourapp.com. The next client would get the app as https://customer2.yourapp.com.

Authentication can differ from using your own authentication db, OAuth to gmail/fb etc or doing an SSO.

To control the users, you would be writing a licensing module that records the user activity, & based on the authentication, you define what data you need to capture.

Hope this answers your question.