> In the demo, a new container is created for every function invocation which would introduce latency that wouldn’t really be acceptable for most user-facing s

> In the demo, a new container is created for every function invocation which would introduce latency that wouldn’t really be acceptable for most user-facing systems. That seems like an implementation issue that can be overcome, an alternative approach could be to spin up a few containers, deploy the function artefact/JAR/script/whatever and then continuously invoke it via a load balancer. Then if the function isn't called for a while, terminate or scale down the container(s) I believe AWS lambda works in a similar way to the above approach.