Azure Functions vs. Google Cloud Functions

It is well suited for REST APIs that need scalable functionality and for hosting microservices with a short life cycle. It is not well suited for Applications that need real-time features or heavy processing, such as image processing or model training, that need to stay up for longer periods and require compute.

Incentivized

Any sort of transaction or complex logic that is going to take longer than 250ms or accesses resources that are protected by permissions, secrets, etc. is a great use case for a GCF. Some sort of "helper function" associated strictly with the UI inside browser would not be a good application of a GCF. It would not be crazy to create/debug some fairly complicated logic inside the browser/IDE and when perfected package it up as a Google Cloud Function. I have done that many times.

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

• integration with oAuth
• integration with Firebase
• integration with React Frontend

Incentivized

• Timing for creating new instances.

Incentivized

• Needing a zip file is problematic (when wanting to automate deployment for example).
• Requires another solution to execute automatically (ex. cloud scheduler).

Incentivized

Sometimes the Azure dashboard can feel confusing at first, and it can be hard to understand where things are. But overall, it has good integrations, is trustworthy for running there without disruptions, is well-documented and easy to implement, especially for newbies on the team, and has nice automated deployment features.

Incentivized

The console UI is pretty nasty. Managing various authentication/permissions configurations is just a nightmare. On the other hand, once you are over the hump it's not so bad. AWS Lambda is no better.

Incentivized

Documentation is provided and clear for this service. Although GCP support is included in the current contract we didn't get to use it since the process is pretty straightforward.

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

It is easier to keep everything in house when we are using GCP or AWS. To mix Lambda with google cloud is not a best practice and will cause problems ahead. The segmentation is clear, if you are using google, you use Google Cloud Functions. if you are on Amazon, you use all AWS tools. You can't mix them. The price is set.

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

• For training purposes, it is free
• Budgeting makes it cap the use
• monitoring makes it predictable

Incentivized