AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
Microsoft Power Automate
Score 8.2 out of 10
N/A
Microsoft Power Automate is an advanced automation platform offering a range of features, including AI-powered automation, robotic process automation (RPA), business process automation (BPA), digital process automation (DPA), and process/task mining. The platform aims to empower organizations to securely automate their operations at scale by leveraging low-code and AI technologies.
$15
per month per user
Pricing
AWS Lambda
Microsoft Power Automate
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Power Automate Premium
$15
per month per user
Power Automate Process
$150
per month per bot
Hosted RPA add-on
$215
per month per bot
Process Mining add-on
$5,000
per month per tenant
Offerings
Pricing Offerings
AWS Lambda
Microsoft Power Automate
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Lambda
Microsoft Power Automate
Features
AWS Lambda
Microsoft Power Automate
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
If you are in a team that needs to develop automated solutions but have no coding experience and no access to a developer, Power Automate is one of the best places to start. It is incredibly flexible and likely has triggers and actions that can connect with your platforms, especially if you use the Microsoft stack. Additionally, using webhooks, you can connect to many different endpoints to get systems working together.
Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
I REALLY wish I could just drop in a block of python or PowerShell code sometimes. The visual low-code things are great for moving around data but sometimes it would be faster if I could just tap out some code.
The DOM (Document Object Model) is not entirely apparent and takes a lot of trial and error, and sometimes it's even different between different connectors. I would love to be able to just see the path to access some specific variables from earlier processes.
The tool is very useful when used with its various native connectors, taking great advantage of the integration between the components and systems of the Office365 universe. However, its cost is still high, and automation using more advanced components containing AI resources becomes unfeasible for some companies. Due to the financial crisis that many companies are currently experiencing, investment in automation systems or tools is taking a back seat.
I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
Power Automate features a clean and intuitive user interface that allows users to create, manage, and monitor workflows easily. The UI is designed to be accessible to both technical and non-technical users, with drag-and-drop functionality for building workflows. Power Automate supports integration with a wide range of Microsoft and third-party applications. This flexibility in integration allows users to automate workflows across various systems, enhancing overall productivity and efficiency.
Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
both Community support and Microsoft official support typically respond to (and resolve) reported issues in a VERY expedient manner, usually going above and beyond for education and bugfixing. I have been thoroughly impressed with the level of support I had been provided in the past.
after reviewing the main features of Power Automate, the Microsoft trainer focused on some of our real life use cases implementation, from simple to more advanced.
although it was productive, it is more difficult to stay focused and in a 7 hours a day online training (including screen share issues and the fact that the trainer just can't precisely show the exact location of your mistake)
I was part of the migration of classic SharePoint workflows and Nintex workflows. We didn't spend much time learning the new platform because of its user-friendly interface and intuitive drag-and-drop functionality. We have mostly O365 E1 and E3 licensed users, so they can participate in our Citizen Development program and utilize Power Automate to build day-to-day business processes.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
I have many years of experience with Nintex applications and it stands up very well against Microsoft Power Automate. I hope Microsoft Power Automate can become the better workflow application. With the Integrated AI builder and continuous updates I expect they can become the better one in a few years.
Microsoft's professional services provide hands-on support throughout the implementation lifecycle of Power Automate.This includes initial setup, configuration, integration with existing systems, testing, and deployment. They ensure that workflows are correctly designed, optimized for performance, and aligned with security best practices.
Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.