User-1643391774 posted
Hi forum,
i am completly new to Microsoft Azure. I want to build a distributed enterprise application and host it on Azure. From what i've learned you should better develop n-tier applications, to better scale your application. So what i want to build is
:
- a web application, but with focus on mobile views, because the web application will be primarily consumed by smartphones
- a backend for persisting data
- a desktop application that interacts with the backend
What i've imagined is to use following technologies/components:
- ASP.NET MVC 5 for the web frontend
- a secure Web API service that implements all the logic
- a SQL database to persist all data
- a WPF application that interacts with the Web Api service (probably with client certificate authentication)
Do you think this is a good architecture? To let the WPF application communicate with the backend i will need the Web Api service in any way. But i am not sure if this pattern also matches the ASP.NET MVC application. If i would develop
an on-premise solution i would let the ASP.NET MVC application communicate with the Web Api service. But i am not sure if this is also needed/correct when hosting on Azure, because Azure is scaling for me behind the scene?!
Next question is if i can use the the normal Visual Studio web templates to create the application on my dev machine and then later host it on Azure or must i use the Cloud templates? And what cloud templates do i need for my application? What's the
difference between a cloud service, an Azure mobile service and an Azure mobile App?
Thanks in advace!
regards,
xxxdevxxx