Azure Functions enables users to execute event-driven serverless code functions with an end-to-end development experience.
N/A
Azure Virtual Machines
Score 8.8 out of 10
N/A
Virtual Machines (VMs) are available on Microsoft Azure, providing what is built as a low-cost, per-second compute service, available via Windows or Linux.
This is the most straightforward and easy-to-implement server less solution. App Service is great, but it's designed for websites, and it cannot scale automatically as easily as Azure Functions. Container Apps is a robust and scalable choice, but they need much more planning, …
Azure Virtual Machines offer unparalleled flexibility in provisioning, managing and upgrading the VM instances, both manually and programmatically. AVM offer very granular billing options and enables high costs optimisations (while still being costly). The other competitors I …
Oracle Cloud Infrastructure's Compute supports Windows, but is really geared towards Linux. You can install Windows on some Linode servers, but again, Linode is geared towards Linux. AWS does everything but is complex and can have high costs.
Azure VM's are far way cost effective than the AWS EC2 service also Azure VM's provides up Smart Hybrid Cloud integration with the Existing on Prem architecture. One of the key feature of Azure VM are they provide High availability and data redundant zones for the VM to be hosted.
We use both Azure and AWS VM services currently. AWS' EC2s have been around for longer an offer a much more reliable Linux OS support. But the gap getting smaller by the day, and Azure VMs are catching up nicely. In our case, we use a lot AWS for Linux-based applications …
Our main reason for selection of Azure Virtual Machines was easy availability of databricks and windows based VM natively. These features are not available on EC2.
Amazon EC2 provides a cost-friendly server hosting platform but the underlying infrastructure of Azure Virtual Machines is way more speedy and responsive than AWS. We have a 40:60 ratio of our servers deployed on Azure and Amazon and I can tell you how responsive and …
Amazon EC2 is useful for easy migration from physical to virtual. While Azure Virtual Machines are very handy to use and the management console is very simple which gives all the important features at a glance of a screen. We have a good presence of virtualization and Windows …
I have tested AWS EC2 instances, however, we chose
Azure Virtual Machines as we use SCOM as an enterprise monitoring solution and it goes very well
with Azure as monitoring. We have a lot of customers on Azure and monitoring the Azure environment with SCOM is easy through
Azure Virtual Machines is much easier to manage and is a user-friendly management console. Billing is much easier and more predictable to calculate and expect, the configuration is much easier to access and change, the cost is cheaper for Azure Virtual Machines than other …
More or less these are comparable offerings in my opinion as a user of both the AWS and Azure Clouds in a business environment in which there's a use case for a multi-cloud environment. We were able to complete a feature parody between the Azure Cloud and AWS Cloud for key …
We also use AWS Cloud Services, personally, I think AWS is a little more expensive than Azure Virtual Machines but its swings and roundabouts mostly. I prefer the interfaces in Azure Virtual Machines as I feel I'm closer to the Machine than with AWS and my roots are from a …
If you have Fffice360 and use Azure for data and other purposes, I will suggest using Azure Virtual Machine for better integration and security. Pros and cons from both, but it's more convenient to stay on the same platform for security and stability.
Azure has a better interface than its competitors like Amazon and IBM. It is more intuitive and easier to use. It also has more features like connection troubleshooting, boot diagnostics, and running remote commands.
Azure Virtual Machines was faster, cheaper, and took up less storage than Amazon EC2 Auto Scaling and is why we continue to use it to this day. We are very satisfied with all that Azure Virtual Machines can do and would recommend it to anyone looking for a virtual machine in …
They're great to embed logic and code in a medium-small, cloud-native application, but they can become quite limiting for complex, enterprise applications.
It's well suited to delivering information about our sports events as during the events a lot of processing power is needed and instantly becomes available by scaling out when the event is over the service can be scaled right back making massive savings. We use it for football, horse racing, Olympics games etc, it is also used when things happen in the world like right now there is a lot of concern over the Russia and Ukraine conflict, since the demand for this information is high we instantly scale to meet the demand of our news feed services. I believe up to 90% of the UK's News, sports and media information actually passes through our computer systems, we are a market leading news and information service and Azure Virtual Machines provide us with the reliability that we need so that we can provide a rock solid reliable news and information service to the world.
They natively integrate with many triggers from other Azure services, like Blob Storage or Event Grid, which is super handy when creating cloud-native applications on Azure (data wrangling pipelines, business process automation, data ingestion for IoT, ...)
They natively support many common languages and frameworks, which makes them easily approachable by teams with a diverse background
They are cheap solutions for low-usage or "seasonal" applications that exhibits a recurring usage/non-usage pattern (batch processing, montly reports, ...)
My biggest complaint is that they promote a development model that tightly couples the infrastructure with the app logic. This can be fine in many scenarios, but it can take some time to build the right abstractions if you want to decouple you application from this deployment model. This is true at least using .NET functions.
In some points, they "leak" their abstraction and - from what I understood - they're actually based on the App Service/Web App "WebJob SDK" infrastructure. This makes sense, since they also share some legacy behavior from their ancestor.
For larger projects, their mixing of logic, code and infrastructure can become difficult to manage. In these situations, good App Services or brand new Container Apps could be a better fit.
Pricing can be a concern if you are truly agnostic to which cloud you are building your particular solution in.
The UI, as is the case with any cloud provider, is crowded.
As with any cloud provider, it can be difficult to tune in exactly the right amount of servers for your needs...you might find yourself under/overprovisioning.
I give the overall support for Azure Virtual Machines a 7 because I think while the overall support do a great job there are still areas that it could improve on such as efficiency and speed. So while I only give it a 7 and it has some issues it is still better than the overall support at Amazon EC2 Auto Scaling.
This is the most straightforward and easy-to-implement server less solution. App Service is great, but it's designed for websites, and it cannot scale automatically as easily as Azure Functions. Container Apps is a robust and scalable choice, but they need much more planning, development and general work to implement. Container Instances are the same as Container Apps, but they are extremely more limited in termos of capacity. Kubernetes Service si the classic pod container on Azure, but it requires highly skilled professional, and there are not many scenario where it should be used, especially in smaller teams.
Oracle Cloud Infrastructure's Compute supports Windows, but is really geared towards Linux. You can install Windows on some Linode servers, but again, Linode is geared towards Linux. AWS does everything but is complex and can have high costs. If you want to host Windows servers in the cloud, nothing beats Azure. From licensing to management, Microsoft Azure provides the easiest way to deploy and manage Windows Servers in the cloud, especially if you utilize other Microsoft services like Microsoft 365 an Visual Studio subscriptions.
They allowed me to create solutions with low TCO for the customer, which loves the result and the low price, that helped me create solutions for more clients in less time.
You can save up to 100% of your compute bill, if you stay under a certain tenant conditions.
It's so easy to spin up new instances, that it becomes also to easy to have to many of them to manage. Many teams end up with a couple of hundreds of VMs after a short while, making the whole thing very hard to maneuver
Azure VMs are the next step for us to rely on Onprem servers, and leaving the management of the infrastructure to the professionals
The ease of use, is also important when our main focus is to deliver new applications and integrations fast, and not having to worry about infrastructure. We sell bottles, not CPUs
