Likelihood to Recommend 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.
Read full review In terms of cloud computing, Microsoft Azure is the only comprehensive result the company offers. Regardless of how big or small an organization is, it can make use of this system. As a cyber-security professional, this is your best option for data management. A business that wants to minimize capital expenditures can use Microsoft Azure. Many Microsoft services accept it. People with little or no knowledge of cloud computing may find it impossible. It isn’t the solution for companies that don’t want to risk having only one platform and infrastructure vendor.
Read full review Pros Lambda provides multiple methods for triggering functions, this includes AWS resources and services and external triggers like APIs and CLI calls. The compute provided my Lambda is largely hands off for operations teams. Once the function is deployed, the management overhead is minimal since there are no servers to maintain. Lambda's pricing can be very cost effective given that users are only charged for the time the function runs and associated costs like network or storage if those are used. A function that executes quickly and is not called often can cost next to nothing. Read full review Azure simply provides end to end life cycle. Starting from the development to automated deployment, you will find [a] bunch of options. Custom hook-points allow [integration] on-premise resources as well. Excellent documentation around all the services make it really easy for any novice. Overall support by [the] community and Azure Technical team is exceptional. BOT Services, Computer Vision services, ML frameworks provide excellent results as compare to similar services provided by other giants in the same space. Azure data services provide excellent support to ingest data from different sources, ETL, and consumption of data for BI purpose. Read full review Cons Putting a significant portion of your codebase into AWS Lambda and taking advantage of the high level of integration with other AWS services comes with the risk of vendor lock-in. While the AWS Lambda environment is "not your problem," it's also not at your disposal to extend or modify, nor does it preserve state between function executions. AWS Lambda functions are subject to strict time limitations, and will be aborted if they exceed five minutes of execution time. This can be a problem for some longer-running tasks that are otherwise well-suited to serverless delivery. Read full review In our experience, Azure Kubernetes Survice was difficult to set up, which is why we used Kubernetes on top of VMs. Azure REST API is a bit difficult to use, which made it difficult for us to automate our interactions with Azure. Azure's Web UI does a good job of showing metrics on individual VMs, but it would be great if there was a way to show certain metrics from multiple VMs on one dashboard. For example, hard drive usage on our database VMs. Read full review Likelihood to Renew Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.
Read full review Usability 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.
Read full review Microsoft Azure's overall usability has been better than expected. Often times vendors promise the world, only to leave you with a run-down town. Not the case with our experience. From an implementation perspective, all went perfect, and from the user-facing experience we have had no technical issues, just some learning curve issues that are more about "why" than "how"
Read full review Reliability and Availability It has proven to be unreliable in our production environment and services become unavailable without proper notification to system administrators
Read full review Support Rating I have not needed support for AWS Lambda, since it is already using Python, which has resources all over the internet. AWS blog posts have information about how to install some libraries, which is necessary for some more complex operations, but this is available online and didn't require specific customer support for.
Read full review Support is easy with all the knowledge base articles available for free on the web. Plus, if you have a preferred status you can leverage their concierge support to get rapid response. Sometimes they’ll bounce you around a lot to get you to the right person, but they are quite responsive (especially when you are paying for the service). Many of the older Microsoft skills are also transferable from old-school on-prem to Azure-based virtual interfaces.
Read full review Implementation Rating As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
Read full review Alternatives Considered Azure Functions is another product that provides lambda functionality, but the documentation for some of Azure's products is quite hard to read. Additionally, AWS Lambda was one of the first cloud computing products on a large cloud service that implemented lambda functions, so they have had the most time to develop the product, increase the quality of service, and extend functionality to more languages. Amazon, by far, has the best service for Lambda that I know.
Read full review As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.
Read full review Return on Investment I was able to perform a lot of processing on data delivered from my website and little or no cost. This was a big plus to me. Programming AWS Lambda is quite easy once you understand the time limits to the functions. AWS Lambda has really good integration with the AWS S3 storage system. This a very good method of delivering data to be processed and a good place to pick it up after processing. Read full review Brings down Capex to customers. Some of the built-in security features of DDoS Basic protection that comes with VNET on Azure or even WAF on AGW brings huge advantages to customers. Hybrid benefits for those who have software assurance can save even more costs by moving to Azure. Read full review ScreenShots