Overview

AWS Lambda

Stacks24.4K

Followers18.8K

Votes432

Vercel

Stacks1.6K

Followers925

Votes86

GitHub Stars0

Forks0

AWS Lambda vs Zeit Now: What are the differences?

Key Differences between AWS Lambda and Zeit Now

AWS Lambda and Zeit Now are two popular serverless computing platforms that provide developers with the ability to deploy and run applications without the need to manage underlying infrastructure. While both platforms offer similar functionality, there are key differences that set them apart.

Pricing Model: One major difference between AWS Lambda and Zeit Now is their pricing model. AWS Lambda bills users based on the number of requests and the duration of computing time, whereas Zeit Now offers different pricing plans based on the number of projects, users, and deployment sizes. This difference in pricing models allows developers to choose the option that best suits their specific usage patterns and requirements.
Ecosystem and Integrations: AWS Lambda is part of the larger Amazon Web Services (AWS) ecosystem, which means it integrates seamlessly with other AWS services such as Amazon S3, DynamoDB, and SNS. On the other hand, Zeit Now has its own ecosystem and integrations, with features like automatic SSL provisioning and continuous deployment from Git repositories. The choice between AWS Lambda and Zeit Now may depend on the specific services and integrations a developer requires for their application.
Programming Languages: AWS Lambda supports a wide range of programming languages, including Node.js, Python, Java, and C#. In contrast, Zeit Now primarily focuses on supporting modern JavaScript frameworks like Next.js and Node.js. Developers with a preference for a specific programming language may choose AWS Lambda if their desired language is not fully supported by Zeit Now.
Scalability and Performance: Both AWS Lambda and Zeit Now offer high scalability and performance, allowing applications to automatically scale up or down based on demand. However, AWS Lambda provides more granular control over performance by allowing developers to configure memory allocation and execution time limits for individual functions. This level of control may be beneficial for applications requiring fine-tuned performance optimization.
Managed Infrastructure: One of the key advantages of serverless platforms like AWS Lambda and Zeit Now is the elimination of infrastructure management. AWS Lambda takes care of provisioning, scaling, and managing the servers on which the functions run, while Zeit Now handles the deployment and scaling of applications. The choice between the two may come down to the level of control and granularity a developer needs in managing the underlying infrastructure.
Vendor Lock-in: When comparing AWS Lambda and Zeit Now, it's important to consider vendor lock-in. AWS Lambda is a part of the larger AWS ecosystem, which means developers may become more tightly tied to the AWS platform when using Lambda. On the other hand, Zeit Now is designed to be more agnostic and can be used with various other cloud providers. This flexibility can be advantageous for developers who want to avoid vendor lock-in and have the freedom to switch cloud providers in the future.

In summary, AWS Lambda and Zeit Now differ in their pricing models, ecosystem and integrations, supported programming languages, scalability and performance options, level of managed infrastructure, and vendor lock-in considerations. The choice between the two depends on the specific requirements and preferences of the developer or organization.

Advice on AWS Lambda, Vercel

Tim

CTO at Checkly Inc.

Sep 18, 2019

Needs adviceon

Heroku

AWS Lambda

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.

The setup

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

357k views357k

Comments

Detailed Comparison

AWS Lambda	Vercel
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.	A cloud platform for serverless deployment. It enables developers to host websites and web services that deploy instantly, scale automatically, and require no supervision, all with minimal configuration.
Extend other AWS services with custom logic;Build custom back-end services;Completely Automated Administration;Built-in Fault Tolerance;Automatic Scaling;Integrated Security Model;Bring Your Own Code;Pay Per Use;Flexible Resource Model	Easy, production-ready deployment with one command; Simple scaling, including auto-scaling; No-Ops; Domains & DNS;
Statistics
GitHub Stars -	GitHub Stars 0
GitHub Forks -	GitHub Forks 0
Stacks 24.4K	Stacks 1.6K
Followers 18.8K	Followers 925
Votes 432	Votes 86
Pros & Cons
Pros 129 No infrastructure 83 Cheap 70 Quick 59 Stateless 47 No deploy, no server, great sleep Cons 7 Cant execute ruby or go 3 Compute time limited 1 Can't execute PHP w/o significant effort	Pros 23 Simple deployment 17 Free tier 13 Free SSL 12 Simple setup 8 Easy custom domain setup Cons 1 Pricing Unclear
Integrations
No integrations available	GitLab GitHub Lighthouse

What are some alternatives to AWS Lambda, Vercel?

GitHub Pages

Public webpages hosted directly from your GitHub repository. Just edit, push, and your changes are live.

DomainRacer

It is a blazing fast hosting solution that provides Customer Satisfaction driven Web Hosting services since 2016.

Netlify

Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment.

Azure Functions

Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.

Google Cloud Run

A managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. It's serverless by abstracting away all infrastructure management.

Surge

Surge makes it easy for developers to deploy projects to a production-quality CDN through Grunt, Gulp, npm.

Webflow

Webflow is a responsive design tool that lets you design, build, and publish websites in an intuitive interface. Clean code included!

Divshot

Divshot makes building and hosting front-end web applications simple. Build locally and deploy using a simple command-line interface. Divshot supports multiple environments, pushState routing, atomic deploys, and more.

Serverless

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.