Flask: Add Zappa To Flask Deploy Guides

[Miserlou]

Since Zappa now integrates seamlessly with Flask, I was wondering if you'd be open to the notion of having Zappa as one of the documented deployment options. I'm willing to write the docs myself, but I wanted to confirm the feature before submitting a pull request. I've also already written a small tutorial if anybody is interested in learning more.

Thanks!

[untitaker]

I'd rather have this outside of the Flask project unless there is sufficient demand for having it baked into the Flask docs.

[davidism]

If this is a well established method of deploying apps, I'd be ok with including a link to external official documentation (more than a blog post) like we do with other services. But the stuff that's included first-party is for more general/traditional server setups.

[davidism]

On second look, how is this different than CGI besides "you don't pay for the server being idle"? It sounds like you're starting an entire process for every request, which would be pretty inefficient.

[Miserlou]

You are, but it's across n-many virtual machines, which are spawned instantly when the HTTP request comes through the API Gateway. It would be inefficient on a single machine, but Amazon automatically handles horizontal scaling and executes the application from memory, so there's no way that requests block each other. Plus, you never have to worry about server maintenance ever again, because the servers only exist for a single HTTP request.

[jeffwidman]

The consensus from the maintenance team is that while we're genuinely excited that Zappa supports Flask, we don't want to have detailed deployment instructions for proprietary/third-party services in the docs. It's too easy for the Flask docs to get outdated when the third-party updates some random config setting.

[Miserlou]

Fair enough, sound reasoning, thanks for considering.