AWS Lambda vs. Azure Container Apps

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

Azure Container Apps is a welcome addition for sure. Based on my experience, this has enabled us to move fully to the cloud and managed everywhere in one spot and on the go. We can scale it to our end as much as we would like. It can be assess anywhere and it is fully secure

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

• Cloud-native where it can be assess anywhere
• Enhance security
• Open source

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

• The deployment process is complicated
• Learning of Azure cli (command-line interface) for deployment is required
• Not compatible with other standard CI/CD tools

Incentivized

I would rather use AKS for my critical applications. The fact that the deployment process is dependent on as cli makes it hard for us to integrate with our standard CI/CD tools

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

Azure Container Apps are fantastic and it is a game changer. I would recommend it to anyone considering it. As you can scale it to what you would like and it is fully cloud native with better security. It is a no brainier not to consider it. I do believe that with further improve it will become even more attractive

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

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

Each one has the benefits and drawback. While it is not easy to compare apple for apple. I definitely like that it can be integrated with our system to ensure that we are running at 100% capacity. It is a vision to be 100% cloud base and we have been able to achieve this through Azure Container Apps

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

• As it is cloud native, we no longer required to have onsite prem
• Reducing both from an energy and security perspective
• It is worth the investment as we have saved about 10% of our ICT cost

Incentivized