I agree with this in general, however to avoid premature optimization it may still be worth building a prototype that is pure serverless, then as you roll it out to high volume production use, some of those functions can be run more effectively (lower latency/cost) by autoscaling permanent containers. If you think about a service containing a bundle of functions, there are likely to be some functions in heavy use, and others that are infrequently invoked, so you are paying the memory overhead of having them sitting around waiting. In some cases that matters, in others it’s not a big deal.

--

--

--

Work: Amazon Sustainability (ex AWS, Battery Ventures, Netflix, eBay, Sun Microsystems, CCL)

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
adrian cockcroft

adrian cockcroft

Work: Amazon Sustainability (ex AWS, Battery Ventures, Netflix, eBay, Sun Microsystems, CCL)

More from Medium

3sixteen

Rest in Treats

How Far Can “the Power of the People Take Us?”

Learning To Juggle