Chalice: Python Serverless Microframework for AWS

I think I would have preferred this to be some type of plugin&#x2F;add-on to Flask rather than a full replacement that now locks me to AWS and is a brand new project without any docs :(<p>If it was a cli with decorators or something that uses Flask I would feel more comfortable and give it a shot.

Ok, I have seen the phrase &quot;serverless&quot; a few times recently. Can someone explain to me what it is (as I am pretty sure it involves a server - it runs on AWS ffs) and why I should want to use it? And most importantly, is it web scale?

AWS Lambda is cool and all, but aren&#x27;t people doing the math on this? Lambda seems like a <i>really</i> expensive way to deliver almost anything. Likewise, the AWS API Gateway is expensive, but at least provides some additional capabilities. Lambda seems like its profitable niche would be very small; limited computing environment, very high cost (relative to almost every other way to host an API), and having to learn a whole bunch of new APIs and processes to make it all spin.<p>Am I missing something?

Question:<p>With these &quot;Serverless&quot; frameworks (Zappa, Chalice, Serverless, etc), do you have to redeploy to Lambda every time you want to test your changes during development?<p>Is there a way to develop locally and get quick feedback?

This is awesome - it takes care of a lot of the pain of setting up Lambda, including the packaging, the tricky IAM policies and the crazy API Gateway incantations. It also follows the Flask decorator conventions!<p>I could have really used this a few months ago. I ended up writing a library of my own, but I&#x27;d much rather have used this, as it&#x27;s supported by the AWS Python team.<p>This really lowers the barrier to entry to deploying Python-based API servers!

Has anyone successfully and painlessly used Lambda+API Gateway in production as their main backend? It appears Lambda has many limitations, but I see rather mature frameworks such as Serverless (formerly JAWS) being promoted here, and now Amazon is also working on their standard framework.<p>It would be great to just use CDNs and this; get all benefits of using a PaaS with IaaS-level costs only!

Serverless computing seems to just be reinventing hosted CGI. Is this not just a trade of Perl and php for Python and JavaScript?

I love the name. :) Fits right in with &quot;flask&quot; (<a href="http:&#x2F;&#x2F;flask.pocoo.org" rel="nofollow">http:&#x2F;&#x2F;flask.pocoo.org</a>) and &quot;bottle&quot; (<a href="http:&#x2F;&#x2F;bottlepy.org&#x2F;docs&#x2F;dev&#x2F;index.html" rel="nofollow">http:&#x2F;&#x2F;bottlepy.org&#x2F;docs&#x2F;dev&#x2F;index.html</a>).

I think this is great! While I&#x27;m no python expert - as much as i love flask - i get annoyed at the parts needed to setup up the uWSGI stuff. It looks like using chalice, maybe i don&#x27;t have to worry about setting up the annoying uWSGI stuff?

Very cool, is it still Python 2.7.x only though like AWS Lambda service &amp; Python code?

Consider <a href="https:&#x2F;&#x2F;getsandbox.com" rel="nofollow">https:&#x2F;&#x2F;getsandbox.com</a> it provides great support for viewing state and route logs. Various hosting options.

What is the recommended way of keeping the URL of the service straight? To set up a DNS pointer to the DNS name amazon generates, with a &quot;low enough&quot; TTL?