Amazon Web Services vs. AWS Lambda

We recommend AWS Lightsail with Plesk Ubuntu Web Admin (free) edition for launching WordPress websites. Pricing starts with 3.5$ per month and they are providing 3 months free. In order to access advanced features of Plesk, consider upgrading to paid Plesk plans that starts with 13.50$ per month (10 websites supported). Up to 40% discount is available for the first year. Anyway, even the free Plesk Web Admin version is by itself self sufficient with free SSL.

[AWS Lambda] is very well suited for the projects that doesn't have any infra but needs it where short running processes are required. But if your application need to run continuously than this might not be the very apt tool for you.

Incentivized

• Starting an instance and accessing it for testing purpose, demo or production deployment its always easy.
• All the things which are available over AWS are pretty well managed and easy to use.
• You might find everything you required for an product and other development over AWS.
• Its suitable for both either an enterprise or an startup
• Various resources and documentation are available in case you struck somewhere.

Incentivized

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

Incentivized

• If there is one thing I think AWS needs improvement on, it is the administration dashboard. It can be a nightmare to use especially when trying to access billing. This could be made better, honestly, as there should be a simplified way to access simple admin features.
• While AWS was fairly easy to integrate into our solutions, it is not as easy to use without some IT knowledge. The dashboards are complicated and designed for someone who is computer savvy. If you are just want to keep track of billing, for example, you may need to take a course or spend a few hours with someone being walked through the admin console.
• AWS does tend to be slow at times. If you do not have a fast internet connection, it can take time to access services that are hosted on AWS. This is not always the case but we have had clients complain about this if they are trying to access a service from multiple points (IP addresses). The only real fix we found was to make our files cache to another server and only keep current data accessible to clients.

Incentivized

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

Incentivized

We are almost entirely satisfied with the service. In order to move off it, we'd have to build for ourselves many of the services that AWS provides and the cost would be prohibitive. Although there are cost savings and security benefits to returning to the colo facility, we could never afford to do it, and we'd hate to give up the innovation and constant cycle of new features that AWS gives us.

Our cloud platform architecture was designed in order to collect, analyze, and optimize modern networks, from AWS-powered computing, networking, storage, and more. So, we needed a reliable, scalable, and secure global computing infrastructure. Auto Scaling and Elastic Load Balancing were key features in our evaluation and later on for scalability and high performance. We being a cybersecurity company, we needed to ensure that our cloud provider utilizes an end-to-end approach to secure and harden the infrastructure, including physical, operational, and software measures - which AWS had all in place.

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

Availability is very good, with the exception of occasional spectacular outages.

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.

The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to
immediately search for their compatible software's and also to guide them in a
good direction. Moreover, this product is a good suggestion for every type of
company because of its affordability and ease of use.

Incentivized

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.

Incentivized

The API's were very well documented and was Janova's main point of entry into the services.

Amazon Web Services is well suited when we have a huge amount of data to store, process, manipulate and get meaningful information out of. It is also suitable when we need very fast data retrieval from the database. They provide a superior product at a fair price which allows us to further our goals and push the limits of what we are capable of as a team / company.

Incentivized

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.

Incentivized

• AWS has lowered our employee cost, because you don't have to hire Network/Server Admins to manage infrastructure.
• Increased productivity by incorporating Continuous Integration with AWS and our development life cycle.
• Increased customer confidence by being able to provide HIPAA level security in our development and production environments

Incentivized

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

Incentivized