AWS Lambda vs Microsoft Azure

• Lambda provides multiple methods for triggering functions, this includes AWS resources and services and external triggers like APIs and CLI calls.
• The compute provided my Lambda is largely hands off for operations teams. Once the function is deployed, the management overhead is minimal since there are no servers to maintain.
• Lambda's pricing can be very cost effective given that users are only charged for the time the function runs and associated costs like network or storage if those are used. A function that executes quickly and is not called often can cost next to nothing.

Read full review

• Azure simply provides end to end life cycle. Starting from the development to automated deployment, you will find [a] bunch of options. Custom hook-points allow [integration] on-premise resources as well.
• Excellent documentation around all the services make it really easy for any novice. Overall support by [the] community and Azure Technical team is exceptional.
• BOT Services, Computer Vision services, ML frameworks provide excellent results as compare to similar services provided by other giants in the same space.
• Azure data services provide excellent support to ingest data from different sources, ETL, and consumption of data for BI purpose.

Read full review

• Putting a significant portion of your codebase into AWS Lambda and taking advantage of the high level of integration with other AWS services comes with the risk of vendor lock-in.
• While the AWS Lambda environment is "not your problem," it's also not at your disposal to extend or modify, nor does it preserve state between function executions.
• AWS Lambda functions are subject to strict time limitations, and will be aborted if they exceed five minutes of execution time. This can be a problem for some longer-running tasks that are otherwise well-suited to serverless delivery.

Read full review

• In our experience, Azure Kubernetes Survice was difficult to set up, which is why we used Kubernetes on top of VMs.
• Azure REST API is a bit difficult to use, which made it difficult for us to automate our interactions with Azure.
• Azure's Web UI does a good job of showing metrics on individual VMs, but it would be great if there was a way to show certain metrics from multiple VMs on one dashboard. For example, hard drive usage on our database VMs.

Read full review

• I was able to perform a lot of processing on data delivered from my website and little or no cost. This was a big plus to me.
• Programming AWS Lambda is quite easy once you understand the time limits to the functions.
• AWS Lambda has really good integration with the AWS S3 storage system. This a very good method of delivering data to be processed and a good place to pick it up after processing.

Read full review

• Brings down Capex to customers.
• Some of the built-in security features of DDoS Basic protection that comes with VNET on Azure or even WAF on AGW brings huge advantages to customers.
• Hybrid benefits for those who have software assurance can save even more costs by moving to Azure.

Read full review