Need advice about which tool to choose?Ask the StackShare community!
Aerospike vs AWS Lambda: What are the differences?
What is Aerospike? Flash-optimized in-memory open source NoSQL database. Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees.
What is AWS Lambda? Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB. AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
Aerospike can be classified as a tool in the "In-Memory Databases" category, while AWS Lambda is grouped under "Serverless / Task Processing".
Some of the features offered by Aerospike are:
- 99% of reads/writes complete in under 1 millisecond.
- Predictable low latency at high throughput – second to none. Read the YCSB Benchmark.
- The secret sauce? A thousand things done right. Server code in ‘C’ (not Java or Erlang) precisely tuned to avoid context switching and memory copies. Highly parallelized multi-threaded, multi-core, multi-cpu, multi-SSD execution.
On the other hand, AWS Lambda provides the following key features:
- Extend other AWS services with custom logic
- Build custom back-end services
- Completely Automated Administration
"Ram and/or ssd persistence " is the top reason why over 9 developers like Aerospike, while over 121 developers mention "No infrastructure" as the leading cause for choosing AWS Lambda.
Aerospike is an open source tool with 296 GitHub stars and 55 GitHub forks. Here's a link to Aerospike's open source repository on GitHub.
According to the StackShare community, AWS Lambda has a broader approval, being mentioned in 1022 company stacks & 613 developers stacks; compared to Aerospike, which is listed in 30 company stacks and 9 developer stacks.
When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:
- Developer Experience trumps everything.
- AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
- If you need geographic spread, AWS is lonely at the top.
Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:
- Pure, uncut, self hosted Kubernetes — way too much complexity
- Managed Kubernetes in various flavors — still too much complexity
- Zeit — Maybe, but no Docker support
- Elastic Beanstalk — Maybe, bit old but does the job
- Heroku
- Lambda
It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?
I chopped that question up into the following categories:
- Developer Experience / DX 🤓
- Ops Experience / OX 🐂 (?)
- Cost 💵
- Lock in 🔐
Read the full post linked below for all details
Pros of Aerospike
- Ram and/or ssd persistence16
- Easy clustering support12
- Easy setup5
- Acid4
- Petabyte Scale3
- Scale3
- Performance better than Redis3
- Ease of use2
Pros of AWS Lambda
- No infrastructure129
- Cheap83
- Quick70
- Stateless59
- No deploy, no server, great sleep47
- AWS Lambda went down taking many sites with it12
- Event Driven Governance6
- Extensive API6
- Auto scale and cost effective6
- Easy to deploy6
- VPC Support5
- Integrated with various AWS services3
Sign up to add or upvote prosMake informed product decisions
Cons of Aerospike
Cons of AWS Lambda
- Cant execute ruby or go7
- Compute time limited3
- Can't execute PHP w/o significant effort1











