AWS Lambda vs. Microsoft Power Automate

Scenarios where AWS Lambda is well suited: 1. When we need to run a periodic task few times in a day or every hour, we may deploy it on AWS Lambda so it would not increase load on our server which is handling client requests and at the same time we don't have to pay for AWS Lambda when it is not running. So, overall we only pay for few function invocations. 2. When some compute intensive processing is to be done but the number of requests per unit of time fluctuates. For example, we had deployed an AWS Lambda for processing images into different sizes and storing them on AWS S3 once user uploads them. Now, this is something that may happen few times every hour on a particular day or may not happen even once on other days. To handle this kind of tasks AWS Lambda is a better choice as we don't have to pay for the idle time of the server and also we don't have to worry about scaling when the load is high. Scenarios where AWS Lambda is not appropriate to use: 1. When we expect a large request volume continuously on the server. 2. When we don't want latency even in case of concurrent requests.

Incentivized

Very useful RPA tools for automating processes with minimal coding and drag-and-drop functionality, with a wide variety of triggers, including scheduled time-based triggers and activity-based triggers, such as modifying a file/list in SharePoint to run a Power Automate flow. Very easy-to-use UI with native integration with every Microsoft product, and a very low automation failure rate for deployed workflows.

Incentivized

• 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.

Incentivized

• Sending confirmation email to clients and user once the flow is triggered.
• Fetching or Dumping files from one location to another if the flow is triggered.
• Schedule flow helps to send alerts and triggers the flow at a specific interval of time to carry out the required task.
• Power Automate also be used to convert any file format to a specific file format and save it to the required location

Incentivized

• 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).

Incentivized

• Steep learning curve.
• It can be slow to develop simple solutions compared to other automation platforms such as Smarsheet.
• Troubleshooting and developing can be frustrating without proper access to edit the code directly.
• Only able to edit through the GUI and with expressions.
• Many ways to do the same thing can be frustrating when you need to rework your flow.

Incentivized

Power Automate is a great product that has a vast array of options on how to use it. Your imagination is the only hurdle with using Power Automate as there is no limit to what can be done with the system. It has brought a lot of value to our business through the use of custom systems, connectors, and streamlining processes.

Incentivized

It is very easy to get started with AWS Lambda and create your first function. The user interface makes it easy to add AWS services to be inputs or outputs to the function, meaning it can be configured in many different ways for different needs. This makes it ideal for various scenarios in AWS.

Incentivized

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.

Incentivized

As this is a product where a great part of errors can be at the source code level, AWS support team doesn't dive that further. I mean they don't evaluate problems more complex related to your code, [which] is totally understandable, but this make[s] debug process more tough and painful.

Incentivized

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.

Incentivized

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.

Incentivized

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)

Incentivized

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.

Incentivized

It's fine, it works as the others would have, except EC2. We are migrating back to EC2 for dedicated compute because we have scaled to a point where we have consistent traffic. The tradeoff of maintaining infrastructure in-house outweighs the benefits of moving quickly through our roadmap.

Incentivized

I have evaluated Microsoft Power Automate against other workflow automation options, including Nintex, Joget, and custom-built solutions. Overall, Power Automate provided the best balance of integration, cost, speed, and governance for our needs. Power Automate is Low-code, rapid development, minimal maintenance, faster changes, and iteration. Compared with Nintex, Power Automate has a strong workflow designer, lower licensing and operational costs, a separate vendor ecosystem, but Power Automate has Native Microsoft 365 integration, included or incremental licensing, and a strong roadmap with AI and Copilot.

Incentivized

• We have simplified log fiie ingestion using Lambda functions. The return has been less time worrying about getting logs from source to ingestion; one the process is in place the team is nearly 100% hands off.
• We have begun taking a more API focused approach by using API Gateway as the interface to business processes and Lambda as the back end compute. Moving away from server based back ends places us on a path to reducing overall spend in compute costs.
• Lambda functions allow us to easily interface with third party services through APIs. This simplifies access management since the function can be granted permissions and access to the function can be gated with API keys and other authentication methods.

Incentivized

• Automating emails for finance and payroll has not only saved hours of work for those departments but lowers the risk of human error.
• Creating workflows and approvals for our goals and bonus system has saved everyone in the organization hours of manual work and MATH!

Incentivized