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

We replaced all the classic SharePoint and Nintex-based workflows with Power Automate. This saved extra licensing costs and getaways from managing legacy workflows. Power Automate Designer is very user-friendly and requires no additional learning curve. We also use it to replace RPA solutions created with other platforms using the Power Automate Desktop application.

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

• No activity disable feature in the workflow, this would have saved lot of time
• Allow turn off feature to not trigger any pending runs in the queue or add new feature to just run pending runs when the workflow is turned off
• Allow easy copy and paste activities from UI

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

For most tasks WinAutomation is great and easy to use. You just set up tasks on a step by step basis and you can even tell the program what to do when there is an error (such as continue with job). Sometimes with complicated web extraction jobs it would be good to be able to easily extract data from the web page source.

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 had to migrate from Robocorp to Power Automate. The automation was using API and sharepoint. So it was better to use Power Automate instead of Robocorp so we did the migration. in some areas the migration was easy but creating flows and making it smaller codes was difficult. Debugging the code was tough so we took lots of time.

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

Power Automate can do many things that most platforms can't do as a 'citizen-developer' with no access to coding tools and deployment. It allows you to develop and deploy low/no-cost automation flows quickly. The blocks in Powert Automate do the API work for you, where you only need to connect the key data points and actions taken.

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