Forum Discussion
Azure Architecture Validation
My developers and I are designing and proposing to develop a multi-tenant Azure application and am seeking assistance from anyone who has done this previously to help validate my approach. We have an existing Access database with VB6 executables installed in approximately 500 sites. For many reasons this is no longer feasible or supportable so we're redeveloping it using SQL Azure and ASP.NET MVC (C#). We do not need assistance with either SQL or ASP.NET.
We do not want to create a VM for each of the 500-plus clients because they do not have the skills and expertise to manage this and from a cursory examination of Azure pricing, this would be cost-prohibitive. At the same time we want to lessen our own support overheads by having a single code base and shared infrastructure.
The client we're developing this application for expects the numbers to grow once we move everything to the cloud so I need to be sure that my architectural approach is solid and that we can simply scale up the infrastructure as needs dictate.
I'm sure there are much bigger multi-tenant applications than this running on Azure but as we haven't done this before we need to be sure we get it right before we start spending any serious money.
Can anyone confirm that this is a valid approach?
1 Reply
Hi Peter
Exciting stuff, but i cant determine what you are actually asking us to validate.
there are many different solutions in Azure depending on your use case.
when spanning accross regions you could consider traffic manager to insure the end users are redirected to the correct datacenter, and then in the backend have inter site connectivity insuring data sync and so on.
feel free to contact me if you would like to discuss this in greater detail.
kind regards
