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
Vultr
Score 8.8 out of 10
N/A
Vultr is an independent cloud computing platform on a mission to provide businesses and developers around the world with unrivaled ease of use, price-to-performance, and global reach.
$2.50
per month
Pricing
AWS Lambda
Vultr
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Block Storage
$1
per month
Cloud Compute
$2.50
per month
Object Storage
$5
per month
Kubernetes Engine
$10
per month
Load Balancers
$10
per month
Managed Databases
$15
per month
Optimized Cloud Compute
$28
per month
Cloud GPU
$90
per month
Bare Metal
$120
per month
Offerings
Pricing Offerings
AWS Lambda
Vultr
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Pricing is based on specifications chosen in each product category. Bandwidth is also included up to a certain amount per month.
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.
I've been with Vultr over 5 years hosting multiple businesses and email related services. I never experienced a significant outage or data loss. Migration has always been successful as well. Support is top tier and IP reputation is clean. I like the choices of OS, ease of platform use and multiple hosting/ region options.
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.
We’ve been extremely satisfied with the service for many years. After trying other providers, we’ve found nothing that matches the reliability and performance—so we’re not likely to switch anytime soon.
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.
easy to use and configure. great bang for the buck. I need an affordable solution to host in the cloud data from systems installed at our client's site with the ability to drill down and change the configuration remotely. Vultr enabled us to do that in an efficient and affordable way.
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.
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
Linode is a more old-school offering. Linode pricing model and infrastructure rely on classic Virtual Machines. What we like about Vultr is that they offer the same at the front, but in the back, the machines are much more flexible and can be tailor-made to our needs, which of course also impacts the costs of running the infrastructure.
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.
