AWS Lambda vs. Azure Machine Learning

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 can be a more unified product. It feels like 10 different tech teams were building it but we're not talking to each other. An example is when the user needs to know what is the next step. Automatically saving a previous state is very helpful as new users are usually not aware of the functionality.

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

• Easy to create the experiment.
• Easy to adopt the best algorithm.
• Efficient way to deploy the model as a web service.
• Centralized platform for the life cycle of machine learning goal.

• 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

• Few models: Even though it has a lot of Machine Learning models, it is quite limited when compared to R. Most Data Scientists still use and prefer R, so the newest models tend to release as R libraries. With Azure ML, we need to wait for Microsoft to evaluate and decide if including a new model is a good idea or not
• Tableau interface: last time I checked there was no easy way to connect with Tableau.
• Cloud based: You always need a good internet connection to use it.

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

Good UX/UI and overall good usability, but it takes a while to get used to the product & platform. The whole design seems fragmented with little in terms of integration with project management tools such as JIRA, or wireframing. Overall it feels like an unfinished product that's meant for teaching more than for production.

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

I'm satisfied with the Azure Machine Learning Studio- it fulfilled my goal in a single channel. Even haven't worr[ied] about the maintenance or any fault tolerance. This provide[s] the user interactive UI to grab the features easily. [Their] support teams also very help[ful], they stand with us at any time.

Not sure

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

The answer is quite simple: Microsoft Azure Machine Learning Workbench is the cheapest and most user friendly analytics tool I have ever seen! Unless you are running a team of data scientists, this is the tool to go. Most functions (marketing, sales, finance, supply chain, logistics, HR, R&D, etc.) could easily integrate Azure ML in its day to day activity.

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

• It is easy to learn and construct, which impacts directly on productivity.
• Good for experimentation and validation for simple models.
• Has a use cost less than the best alternatives in the market.

Incentivized