Amazon Elastic Compute Cloud (EC2) vs. Azure Functions

Suitable for companies that are looking for performance at a competitive price, flexibility to switch instance type even with RI, flexibility to add-on IOPS, option to lower running cost with the regular introduction of new instance type that comes with higher performance but at a lower cost.

Incentivized

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.

Incentivized

• Huge Diverse range of machine shapes are available which cater to our demand.
• Ability to combine the machines and integrate them with any other service in AWS (Ex: RDS, S3)
• Handling performance and scalability using auto-scaling, ELB configuration and high performance machine shapes.

Incentivized

• 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, ...)

Incentivized

• The choices on AMIs, instance types and additional configuration can be overwhelming for any non-DevOps person.
• The pricing information should be more clear (than only providing the hourly cost) when launching the instance. AWS DynamoDB gives an estimated monthly cost when creating tables, and I would love to see similar cost estimation showing on EC2 instances individually, as not all developers gets access to the actual bills.
• The term for reserving instances are at least 12 months. With instance types changing so fast and better instances coming out every other day, it's really hard to commit to an existing instance type for 1 or more years at a time.

Incentivized

• 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.

Incentivized

You an start using EC2 instances immediately, is so easy and intuitive to start using them, EC2 has wizard to create the EC2 instances in the web browser or if you are code savvy you can create them with simple line in the CLI or using an SDK. Once you are comfortable using EC2, you can even automate the process.

Incentivized

AWS's support is good overall. Not outstanding, but better than average. We have had very little reason to engage with AWS support but in our limited experience, the staff has been knowledgeable, timely and helpful. The only negative is actually initiating a service request can be a bit of a pain.

Incentivized

Amazon EC2 is super flexible compared to the PaaS offerings like Heroku Platform and Google App Engine since with Amazon EC2, we have access to the terminal. In terms of pricing, it's basically just the same as Google Compute Engine. The deciding factor is Amazon EC2's native integration with other AWS services since they're all in the same cloud platform.

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.

Incentivized

• It reduced the need for heavy on-premises instances. Also, it completely eliminates maintenance of the machine. Their SLA criteria are also matching business needs. Overall IAAS is the best option when information is not so crucial to post on the cloud.
• It makes both horizontal and vertical scaling really easy. This keeps your infrastructure up and running even while you are increasing the capacity or facing more traffic. This leads to having better customer satisfaction.
• If you do not choose your instance type suitable for your business, it may incur lots of extra costs.

Incentivized

• 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.

Incentivized