Azure Virtual Machines and App Services are the two basic pillars of Azure cloud services. Both offerings provide a way for you to execute workloads or host your server in the cloud. In both, you pay for some virtual machine in an Azure data center that runs your code. But that’s where the similarities end. One is bare bones infrastructure, whereas the other is a managed platform. One is customizable but hard to manage, whereas the other requires forces you to use the specific tooling and configuration Azure offers.
We’re continuing our journey to go over the best modern web technologies by Microsoft for building a web application, and now it’s time to actually have your app make its way to the internet. We’ll see many Azure offerings, what they support, their pros and cons, and when one is better than the other.
Did you notice that Microsoft announces a new and amazing web framework each year? As the years go by, we get more and more technologies. It's getting hard to keep track of them. In this article series, we'll go over all the ways to build a web application using Microsoft technologies and try to make some order in the mess.
There are so many different ways to create a web application today, it's staggering. In this post, we'll try to make some semblance of order. We'll go over the most popular technology choices in each layer of web application development, and see their pros and cons. That includes the client-side tech, the backend server, the ways to deploy to Azure, the CI/CD pipeline, the database, and the login mechanism.
Every once in a while you need to add telemetry, logging, or metrics. While necessary, writing this code along with the business logic feels kind of wrong. In these cases, you can utilize attributes and ASP.NET Core middleware.