Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs Nuclio: What are the differences?
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; Nuclio: Real-time serverless platform. nuclio is portable across IoT devices, laptops, on-premises datacenters and cloud deployments, eliminating cloud lock-ins and enabling hybrid solutions.
AWS Lambda and Nuclio can be primarily classified as "Serverless / Task Processing" tools.
Some of the features offered by AWS Lambda are:
- Extend other AWS services with custom logic
- Build custom back-end services
- Completely Automated Administration
On the other hand, Nuclio provides the following key features:
- Real-time performance
- Simple debugging, regression and a multi-versioned CI/CD pipeline
- Supports a large variety of open or cloud-specific event and data sources with common APIs
Nuclio is an open source tool with 2.83K GitHub stars and 256 GitHub forks. Here's a link to Nuclio's open source repository on GitHub.
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 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
Pros of Nuclio
- Enterprise grade1
- Air gap friendly1
- Actively maintained and supported1
- Variety of runtimes1
- Variety of triggers1
- Secure image building1
- Scale to zero1
- Autoscaling1
- Parallelism1
- Performance1
- Open source1
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Lambda
- Cant execute ruby or go7
- Compute time limited3
- Can't execute PHP w/o significant effort1
Cons of Nuclio
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is Nuclio?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Nuclio?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Lambda?
What tools integrate with Nuclio?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23+42