I am starting a new enterprise web application. It will be hosted up on Windows Azure and will be an asp.net MVC application talking to an SQL database.
My question relates to multi-tenancy and the correct way to accomplish it. In the past I've created a multi-tenant application by having a tenant table and than putting a TenantID column in every table. This worked fine (but it was only on a smaller scale so it didn't really exercise it to the nth degree). Looking into the multi-tenant stuff on Azure, it doesn't seem to recommend this way. They talk about subdomain, splitting tenants etc. To me, that just seems like a management nightmare. I would like the user to hit a website, enter their tenant login details and boom they are off.
- Is there a simpler way to implement multi-tenancy in Azure that still allows me to use Azure's scalability strengths?
- Should I just use the simple TenantID method? Will the Azure framework still scale well to suit?
- Should I worry about tenancy at the start or just leave it till the end?
Advice needed.
Thanks