Hi,
Can anyone help me with this questions?
What is the best way to deploy Asp.Net Boilerplate + Zero project (SAAS) to Azure App Services and get better scalability system?
PS: My project can run on-promises too.
Of course, i will put database on SQL Database Azure service or on-promises Database.
Questions:
Should i put all projects on same APP Service?
Should i split projects between APP Service / API App?
If yes, What project shoud i put on App Service and API App?
Example: Web to App service , all others (Application, WebApi, Core, EntityFramework) to API App
Anyone has a template project for Aspnetboilerplate+Zero with Azure integration?
Anyone using Continuous Integration with VS Online?
Thanks.
Vitor Lacerda
3 Answer(s)
-
0
If I were you, I would just keep things simple and do Visual Studio Web Deploys to Azure Websites and use Azure Sql. Treat it like any normal web app.
-
0
Hello Vitor, I would recommend you to use Azure on one App, it pretty much scales itself. - You usually don't need to split it.
I do use continuous integration with VS Online (took me about 1h to set up). One of the best features is, that it does all the testing before it provisions to azure web. - So if you use testing, this is a good option for you. But it has it's merits too. I once tried to publish a website with visual studio which was at the same time connected via continuous integration. This went horribly wrong and I worked for hours to get back a working version.
So my recommendation is to use continuous integration, if you do test a lot. (If you use a msdn subscription for the licensing be aware of the 5 builds per day limit). If not, you can use VS to publish to azure, it's easier to maintain.
-
0
thanks guys, I will follow the recommendation to keep in one app.
and will test the functionality of continuous integration just to know better.
Vitor
