Stacks737

Followers776

+ 1

Votes20

Zappa

Stacks52

Followers63

+ 1

Votes0

Add tool

Serverless vs Zappa: What are the differences?

Developers describe Serverless as "The most widely-adopted toolkit for building serverless applications". 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. On the other hand, Zappa is detailed as "Deploy all Python WSGI applications on AWS Lambda + API Gateway". Zappa makes it super easy to deploy all Python WSGI applications on AWS Lambda + API Gateway. Think of it as "serverless" web hosting for your Python web apps. That means infinite scaling, zero downtime, zero maintenance - and at a fraction of the cost of your current deployments!.

Serverless and Zappa belong to "Serverless / Task Processing" category of the tech stack.

Serverless is an open source tool with 30.5K GitHub stars and 3.38K GitHub forks. Here's a link to Serverless's open source repository on GitHub.

Decisions about Serverless and Zappa

Tim Nolet

Founder, Engineer & Dishwasher at Checkly · a year ago | 13 upvotes · 51K views

Shared insights

(

)

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

Pros of Serverless

Pros of Zappa

11
API integration
6
Supports cloud functions for Google, Azure, and IBM
2
Lower cost
1
Auto scale
0
Openwhisk

No pros available

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is 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.

What is Zappa?

Zappa makes it super easy to deploy all Python WSGI applications on AWS Lambda + API Gateway. Think of it as "serverless" web hosting for your Python web apps. That means infinite scaling, zero downtime, zero maintenance - and at a fraction of the cost of your current deployments!

What companies use Serverless?

What companies use Zappa?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Serverless?

What tools integrate with Zappa?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Dubsmash: Scaling To 200 Million Users With 3 Engineers

Dec 14, 2017 at 10:02AM

Dubsmash

+47

66759

What are some alternatives to Serverless and Zappa?

AWS Lambda

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.

Terraform

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Kubernetes

Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Cloud Functions for Firebase

Cloud Functions for Firebase lets you create functions that are triggered by Firebase products, such as changes to data in the Realtime Database, uploads to Cloud Storage, new user sign ups via Authentication, and conversion events in Analytics.

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.

See all alternatives

Interest over time

Serverless vs Zappa