Zappa vs Serverless Framework
An AWS-themed comparison between Zappa and Serverless Framework.
Comparing Apples to Oranges
This comparison isn't a 1-to-1 match, it's like comparing apples to oranges. Specifically, Zappa focuses almost exclusively on deploying WSGI applications in AWS, while Serverless Framework is a general purpose tool for handling all aspects of serverless deployment across multiple platforms. In fact, both tools are awesome and there's no reason why you couldn't use them together.
| Topic | Zappa | Serverless |
|---|---|---|
| Fun to use | 👍 | 👍 |
| Uses CloudFormation under the hood | 👍 | 👍 |
| Export to CloudFormation | ❌ | 👍 |
| Can map to API Gateway | 👍 | 👍 |
| Can map to AppSync (GraphQL schema, resolver templates) | ❌ | 👍 |
| Per-function Python requirements | ❌ | 👍 |
| Python bundling environment | Dev environment / pre-compiled packages | docker-lambda |
| Challenge of integrating non-Python components | Hard | Easy |
| Omission of Packages (pytest, debug tools, et al) | manual | noDeploy directive |
| Websockets | ❌ | 👍 |
| Django settings configuration | Standard | Standard for API Gateway or settings.configure for AppSync |
| Running Django management commands | 👍 | 👍 but undocumented |
| Roles per function | ❌ | 👍 |
| Asynchronous Task Execution | custom/Boto3 | Boto3 |
| Resource provisioning | Web server focused, still need Cloudformation or Serverless Framework | Everything |
| Stage handling | List of configuration objects (zappa_settings.json) | Variables following any pattern |
| Configuration language | JSON | YAML means comments! |
| Keep Warm | 👍 | 👍 |
| Slim handler | 👍 | 👍 |
| Plugin System | ❌ | 👍 |
| Underlying language | Python | Node.js |
Copyright © 2018 Daniel and Audrey Roy Greenfeld.
Site Map