A great tool for the right job
Rating: 8 out of 10
November 01, 2023
DD
Vetted Review
Verified User
4 years of experience
Azure Functions are the first step in the server-less offering on Azure. They are a tool in the Azure Solution Architect toolbox, and they come handy whenever you have to execute a small-medium amount of logic in a broader cloud-native process, or as a minimal, cost-effective backend, for example for a mostly static website.
- 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, ...)
87.5%
8.8
100%
10.0
70%
7.0
- 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.
- Azure App Service, Azure Container Apps, Azure Container Instances and Azure Kubernetes Service (AKS)
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.
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.