What I don't get about these things is how can they be performant. If for every action you are loading an entire runtime, executing something, and then throwing the runtime away you are paying the cost of starting the runtime every time. It gets worse the more actions you execute per second.<p>So then you build a "serverless" thing and then it needs scale at which point you have to rewrite the whole thing as a classic "serverful" application that loads the runtime once, caches stuff, etc. So why not just build it right and with proper discipline the first time?