Azure Functions vs. Cloudflare Workers

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

Good: really best in breed for lambda on the edge. it's much easier to make complex redirects decisions in JS rather than using rewrite rule syntax Good: wrangler CLI for local development Bad: no built-in retentions of logs and it's still hard to troubleshoot issues on the edge

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

• 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

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

• 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