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
DigitalOcean Droplets
Score 9.3 out of 10
N/A
DigitalOcean's Droplets is designed to help the user spin up a virtual machine in just 55 seconds. Standard, General Purpose, CPU-Optimized, or Memory-Optimized configurations provide flexibility to build, test, and grow an app from startup to scale.
$4
per month
Pricing
AWS Lambda
DigitalOcean Droplets
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Basic
$4
per month
CPU-Optimized
$42
per month
General Purpose
$63
per month
Memory-Optimized
$84
per month
Storage-Optimized
$131
per month
Offerings
Pricing Offerings
AWS Lambda
DigitalOcean Droplets
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 for DigitalOcean Droplets varies depending on the size of the virtual environment and the associated data needs.
More Pricing Information
Community Pulse
AWS Lambda
DigitalOcean Droplets
Features
AWS Lambda
DigitalOcean Droplets
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.
DigitalOcean Droplets are the best choice for developers teams that need reliable Linux servers to deploy their projects, the ability to create a droplet for testing purposes then destroy it, and only get charged for the few hours used makes the chances of messing up very slim. DigitalOcean Droplets is a great solution because the servers are scalable and the process of adding more resources like CPU or RAM to an existing droplet takes only a few minutes and once a server is scaled up it can also be scaled down if necessary which is perfect for supporting a temporary peak in traffic for example.
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.
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
DigitalOcean Droplets is continuously evolving to be more and more powerful. It has great features and has low cost options, which is really great for developers. Its CDN, Loadbalancer, etc. make it a good place to host a high-traffic application. Moroever, DigitalOcean Droplets has a nonprofit program that helps nonprofit sites to run their infrastructure, which is tremendous and no competitor of DigitalOcean Droplets does that.
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.