Just want to say, I ran across your framework very quickly after getting an echo dot. One downside is it also does this, even if your zip is less than 50M, making initial setup more complex. Chalice CLI consists of really great utility functions allowing you to perform a number of operations from running locally to deploying in a Lambda environment. Chalice is a framework from AWS for writing serverless applications in Python. It achieved this through the use of Node.js shims that are injected into the build process. Compared to Apex, Up has added a whole bunch of new features, including support for multiple providers and built-in middlewares. With the addition of Serverless Enterprise, you are able to monitor your deployments seamlessly, as well as gain valuble alerts on how your environment is performing. As you start using more and more pieces, you may find that maintaining your tooling is a full-time job in itself. You configure your functions and other related AWS resources in a serverless.yml file, which is then compiled to CloudFormation and deployed as a CloudFormation stack. He's available virtually everyday on Slack https://slack.zappa.io/ and has cultivated an impressive community for Zappa. When Lambda-API Gateway first came out, I spent a long time figuring out how to make things work, and I ended up with many of the same patterns that the author accuses Chalice of stealing - before looking at Zappa, and long before Chalice came out. I'd just like to say that it looks an exceptionally well built and thought out project. One of the big ones in my mind is the fact that you can only enable authorizations at the API level, not the function level. Tons of people have tons of questions and answers on all sorts of topics. Zappa is trying to simultaneously appease two goals: Flask/Django integration and lambda integration. I wanted one open function, and the rest protected. The Serverless Framework has a provider-agnostic way to define serverless applications. Yeah, it's okay now. The Serverless Application Model (SAM) is an extension to CloudFormation within AWS. Zappa - Deploy all Python WSGI applications on AWS Lambda + API Gateway. Personally, I don't think serverless is a panacea. Chalice is deliberately minimalistic, opinionated, and tightly integrated with botocore on Python. Don't underestimate the benefit of a large community and ecosystem that is adding new features and fixing bugs. Once you are satisfied with the plan, then you must run the `up stack apply` command to actually apply the changes. > Zappa does not lock you in to the AWS ecosystem. Terraform is an unopinionated cloud deployment tool. It provides a way to use CloudFormation syntax to define your Serverless Applications with the addition of three new CloudFormation resources Function, API, Table, though it can only be used within the AWS ecosystem. I'm basing a project on it to post here Real Soon Now. This name should be unique. Developers can use Lambda to execute their code in the cloud. One interesting capability Up offers, is the ability to separate the planning and the application of configuration changes. Now that I've written this to clear up the confusion (people were constantly me asking about the differences), I think I can move on. backend get stuck?). Positive: Seamless support for 50M+ files. I couldn't do it with Zappa. If you have been using Node.js then you probably knows TJ or have used one of his libraries already. It goes the other way too. To the “batteries-included” approach of shipping an auto-generated data access layer for DynamoDB tables. Seriously, this is not how I want to be building software! Where do you get such sense of entitlement? Depending on the event sources you would like to use, you also need to provision the necessary EventSourceMapping in order to use Lambda with the likes of Kinesis Streams and SQS. The AWS support itself is built as a plugin, as are all the other providers it supports – Azure, GCP, IBM OpenWhisk, CloudFlare, Kubeless, Fn, and Spotinst. https://github.com/awslabs/aws-serverless-express, https://github.com/awslabs/chalice/issues/27, https://github.com/awslabs/chalice/graphs/contributors. I do appreciate the person at Amazon who gave it to me though for thinking of me. I'm completely sold on the value of lambda functions, but it's viciously complex to actually deploy something simple. The serverless framework is then just a software project that builds upon serverless principles, and that can work with AWS Lambda (amongst others). MongoDB Stitch. 60% Upvoted. The new-project command created a sample app that defines a single view, /, that when called will return the JSON body {"hello": "world"}.. If you make it too hard to migrate to another cloud platform you become completely dependent on Amazon, their pricing, and the choices they make. I will be using it in the future for sure. If you're already using Flask or Django, this can be really handy. Open source projects are always about social credits or doing something for the fun of doing it. It enables "infrastructure as code". That means infinite scaling, zero downtime, zero maintenance - and at a fraction of the cost of your current deployments!. What is Zappa? Choose Chalice if: you specifically need something only Chalice can do; are just starting a new API from scratch; just want to keep it simple; Choose Zappa if: you suspect your API will be somewhat large; already have an API in Flask or Django; your API is core to your product If they fit the use case you're looking for and you prefer their design, you should use them!