🌎 Community-curated list of tech conference talks, videos, slides and the like — from all around the world

🎤

Pay-per-use – we all like it, right? It’s one of the core principals of serverless, but it can also be a challenge. How can we plan our monthly budget if we don’t know what our bill is going to look like? What are we really spending our money on? And of course, what needs to be monitored? Pay-per-use is one of the major drivers of serverless adoption. Small startups love it because their monthly bill is almost zero. Large organizations are attracted to improving their IT spending when the old servers have very low utilization and are mostly idle. While it sounds promising, it also produces a massive challenge – paying-per-use means that you don’t know how much you are going to pay – because most of us don’t know exactly how much we are going to use. In addition, new and unique challenges arise – a bug in the code can suddenly lead to a very high cloud bill, as well as an external API that has a very slow response – causing us to pay for this entire time.
This page was generated from this YAML file. Found a typo, want to add some data? Just edit it on GitHub.