<story><title>Chalice: Python Serverless Microframework for AWS</title><url>https://aws.amazon.com/blogs/developer/preview-the-python-serverless-microframework-for-aws/?sc_channel=sm&amp;sc_campaign=launch_sdk_tools_4a8efa18&amp;sc_publisher=tw_go&amp;sc_content=Python_Microframework&amp;sc_country=global&amp;sc_geo=global&amp;adbsc=social_launches_20160711_63715856&amp;adbid=752600622390587393&amp;adbpl=tw&amp;adbpr=66780587</url></story><parent_chain><item><author>collyw</author><text>Ok, I have seen the phrase &amp;quot;serverless&amp;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?</text></item></parent_chain><comment><author>nashadelic</author><text>Well, if you look at how we&amp;#x27;ve done things over the years:&lt;p&gt;- We used to have our own machines in our own data centers&lt;p&gt;- Then we started renting machines in data centers&lt;p&gt;- We then moved to the cloud model where we would get compute capacity on demand. But the minimum unit was an hour&lt;p&gt;- But what if you could deploy your code and you were only charged for the compute and memory you take for the fulfillment of that request? That is what the &amp;quot;serverless&amp;quot; model is. You don&amp;#x27;t constantly run a server like apache; instead, when you receive a user Request, the relevant function is called, executed and results returned to the user. You are billed for the ram ⨉ CPU.&lt;p&gt;This has many benefits:&lt;p&gt;- For low traffic sites, this has significant cost savings&lt;p&gt;- For high traffic sites, this is auto-scaling without thinking about launching machine instances&lt;p&gt;This isn&amp;#x27;t without problems, naturally. This lends itself well to certain type of problems better than others. For example, if you need lots of hot-cache data, the response times on a serverless stack would be slower.&lt;p&gt;But as you can see from the above, this is the logical direction cloud computing will evolve. Infrastructure will truly be shared and you should be able to extract efficiencies down to the minute.</text></comment>
<story><title>Chalice: Python Serverless Microframework for AWS</title><url>https://aws.amazon.com/blogs/developer/preview-the-python-serverless-microframework-for-aws/?sc_channel=sm&amp;sc_campaign=launch_sdk_tools_4a8efa18&amp;sc_publisher=tw_go&amp;sc_content=Python_Microframework&amp;sc_country=global&amp;sc_geo=global&amp;adbsc=social_launches_20160711_63715856&amp;adbid=752600622390587393&amp;adbpl=tw&amp;adbpr=66780587</url></story><parent_chain><item><author>collyw</author><text>Ok, I have seen the phrase &amp;quot;serverless&amp;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?</text></item></parent_chain><comment><author>dkarapetyan</author><text>It&amp;#x27;s just marketing hype. As you noted there is no such thing as serverless. It is another architecture that forces you to use AWS Lambda and API gateway and a few other services to glue everything together. The idea being that if you are just shuttling bytes back and forth then the overhead of the traditional deployment is too much and you&amp;#x27;re better served with what looks like an event bus with some transformers sitting in the middle.</text></comment>