Azure Cloud Services vs. Google Cloud Functions

Microsoft Azure Cloud services is a good choice for hosting web applications, based on requirements it can be simple websites or complex web services as well as it provides automating application development and deployment pipeline. It's less appropriate in case of cost-effective option for organizations with tight budget constraints. For very basic static websites, Microsoft Azure's offerings might be seen as overkill.

It is easy to use, in 15 minutes you just have to follow a few steps, do some easy configurations and you have the project ready to run, once it is connected to the codebase, the execution is automatic. For anyone coming into the google environment, Functions make code execution easy and transparent. CI/CD is perfect

Incentivized

• Effective service management and performance monitoring capability.
• Reliable security management with excellent access controls.
• Best orchestration and easy configuration management.
• Easy on compatibility testing and change management.

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

Incentivized

• Latency and bandwidth as we often see gap here
• There were many challenges as a developer while migrating our DB from on prem to cloud
• System downtime is also one issue that can be improved

Incentivized

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

Incentivized

As a certificate developer and consultant, I love using Azure, it's interface is developer friendly with well guidance and support. Also there are a lot of service for any work, Azure ecosystem is sufficient to complete your all developments needs. So based on that I feel Azure is good and gives better developer experience.

Incentivized

Overall Google Cloud Functions is losing a lot of benefits to other GCP services, making it less attractive to users. A simple example would be the need to zip application files and push them to Google Storage which makes it a bit complicated to automate via a CI/CD pipeline. Another "similar" solution would be using Cloud Run although the need for a docker image is there, with the recent evolutions to Cloud Run (ability to downscale to 0) it makes a lot more interesting.

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

I feel AWS offers a robust and versatile platform for cloud infrastructure and services. It's scalability, reliability array of tools make it a top choice for businesses of all sizes. AWS has better open source communities such as Linux, Jenkins and GitHub in comparison to Azure service cloud

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

• Azure's services and automation capabilities contribute to operational efficiency.
• Azure's scalability ensures optimal performance during peak demand periods and cost savings during off-peak times

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

Incentivized