AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
Cloudways
Score 9.7 out of 10
N/A
Cloudways, by DigitalOcean, offers a range of managed hosting solutions, including managed Wordpress, Drupal, Joomla, Magento, and others, with a choice of infrastructure providers and media delivery via CloudwaysVPN, and CloudwaysBot notification system.
$10
per month
Pricing
AWS Lambda
Cloudways
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Starting Price
$10.00
per month
Maximum Price
$274.33
per month
Offerings
Pricing Offerings
AWS Lambda
Cloudways
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
$25 per application
Additional Details
—
Cloudways offers 1 free migration to all customers. For any further migration needs the customer can use our free WordPress migration plugin and do it themselves. Or they can request paid migration services for any PHP based application, which start at $25 per application.
More Pricing Information
Community Pulse
AWS Lambda
Cloudways
Features
AWS Lambda
Cloudways
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
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.
When you dont know how to set up a cloud server technically, (The LAMP stack or the PHP settings etc) Cloudways comes handy. You can easily modify the server settings with one click.
Less Appropriate - If you want to save costs, go for direct cloud providers. Setting up technical stuff is a one time job.
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.
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.
They are constantly improving their dashboards and interface to make it easier to use and find the things that we use the most. It's a lot of features to pack in to one UI and they have done a great job of making it user friendly. Their layout is intuitive and easy to learn and is extremely granular. We are able to control every aspect of our websites and applications from an individual level from scaling, to cache, to DNS, security, WAF, and everything in between.
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.
Technical support is just 2-3 clicks away and the Cloudways homepage and the operators are available almost 24/7. They also are able to answer any kind of question related to their services, whether economical or technical. I sometimes made mistakes while using their services and they have been keen to help me, and fixed my problems really fast.
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
Whilst all the top hosting companies have good customer service. Hostinger is the winner here for me. SiteGround has fast servers, but fees increase significantly in year two. CloudWays has excellent support at a lower price than SiteGround. They win over the other two companies because they make it very simple to manage site hosting, specifically for VPS/cloud hosting. You do not need to be as technical as you would if you're a customer of Hostinger and SiteGround. So, in short, for a fast-growing website with 6k+ sessions per month (low WP maintenance experience), I'd choose Cloudways.
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.
