AWS Lambda vs Microsoft Azure

• AWS Lambda is a welcoming platform, supporting several languages, including Java, Go, PowerShell, Node.js, C#, Python, and Ruby. And if you need to deploy a Lambda function in another language, AWS offers a Runtime API for integration.
• We really appreciate how AWS Lambda is always-on for our functions, with only a brief "cold-start" waiting period the first time a function is called after being dormant.
• In addition to only generating costs when it's actually being used, AWS Lambda really puts the "serverless" in serverless architecture, offering turnkey scaleability and high availability for our code with zero effort on our part.

Read full review

• Azure Functions is the easiest serverless service to work with in my experience. Easy to ship Node.js functions without bundling dependencies.
• Proactive and responsive support. We've worked with most other cloud providers - Amazon, Google, Oracle. Amazon Web Services' customer support is a black hole and their documentation is worthless. Google and Oracle are better, but Azure's support is responsive and their docs are pretty good.
• Azure's Web UI is pretty easy to work with

Read full review

• The UI and Developer experience is not so great. IF you use an abstraction like Serverless Application Model (SAM), things get pretty easy, but it's still AWS UI/DX you're working with after that (which is to say, not their strength).
• Documentation is always a mixed bag. Sometimes it's just easier to google your specific problem and see how others have solved it. This can be much faster than trying to find an example that may or may not be there in the documentation (which oftentimes has multiple versions and revisions).

Read full review

• Could be easier to setup redundancy
• Feels as if there are too many options, bells, and whistles you could add.
• Microsoft Azure functions does not have a "Configure Services" method. Programming Azure functions has a slightly different programming model than does a "normal" API application. I would prefer that the startup process be identical.

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

• It has taken a few years of planning and growth (which continue), but we've been able to successfully budget and plan for ever increased capacity by starting first with some Virtual Machines and factoring in on-prem maintenance vs cloud constant improvements. VM (server, compute, networking) costs even out quickly over time and will show savings very soon.
• Because of Azure Application Gateways (which cost very little to set up and maintain), we were able to build a state of the art single-sign-on hub for all of our users and other enterprise platforms (mostly non-Microsoft and non Azure systems), reducing the amount of time to switch among these for workers and increasing overall productivity.
• With Azure Active Directory, we do not need to maintain separate identity systems and can more easily integrate our organizations credentials into authorization for access to other systems.

Read full review