AWS Lambda vs. Azure Machine Learning

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.

Incentivized

For [a] data scientist require[d] to build a machine learning model, so he/she didn't worry about infrastructure to maintain it.

All kind of feature[s] such as train, build, deploy and monitor the machine learning model available in a single suite.

If someone has [their] own environment for ML studio, so there [it would] not [be] useful for them.

• No provisioning required - we don't have to pay anything upfront
• Serverless deployment - it gets executed only when request comes and we pay only for the time the request is getting executed
• Integrates well with AWS CloudWatch triggers so it is easy to setup scheduled tasks like cron jobs

Incentivized

• User friendliness: This is by far the most user friendly tool I've seen in analytics. You don't need to know how to code at all! Just create a few blocks, connect a few lines and you are capable of running a boosted decision tree with a very high R squared!
• Speed: Azure ML is a cloud based tool, so processing is not made with your computer, making the reliability and speed top notch!
• Cost: If you don't know how to code, this is by far the cheapest machine learning tool out there. I believe it costs less than $15/month. If you know how to code, then R is free.
• Connectivity: It is super easy to embed R or Python codes on Azure ML. So if you want to do more advanced stuff, or use a model that is not yet available on Azure ML, you can simply paste the code on R or Python there!
• Microsoft environment: Many many companies rely on the Microsoft suite. And Azure ML connects perfectly with Excel, CSV and Access files.

Incentivized

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

Incentivized

• It would be great to have text tips that could ease new users to the platform, especially if an error shows up
• Scenario-based documentation
• Pre-processing of modules that had been previously run. Sometimes they need to be re-run for no apparent reason

Incentivized

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.

Incentivized

Easy and fastest way to develop, test, deploy and monitor the machine learning model.

- Easy to load the data set

-Drag and drop the process of the Machine learning life cycle.

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.

Incentivized

Support is nonexistent. It's very frustrating to try and find someone to actually talk to. The robot chatbots are just not well trained.

Incentivized

Not sure

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

Incentivized

It is easier to learn, it has a very cost effective license for use, it has native build and created for Azure cloud services, and that makes it perfect when compared against the alternatives. As a Microsoft tool, it has been built to contain many visual features and improved usability even for non-specialist users.

Incentivized

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

Incentivized

• Productivity: Instead of coding and recoding, Azure ML helped my organization to get to meaningful results faster;
• Cost: Azure ML can save hundreds (or even thousands) of dollars for an organization, since the license costs around $15/month per seat.
• Focus on insights and not on statistics: Since running a model is so easy, analysts can focus more on recommendations and insights, rather than statistical details

Incentivized