> So a DNS server can basically take an incoming request, boot up a unikernel in 20 ms, reply with the unikernel IP, and the newly started unikernel will receiv

> So a DNS server can basically take an incoming request, boot up a unikernel in 20 ms, reply with the unikernel IP, and the newly started unikernel will receive the actual request data shortly thereafter. You might be interested in our paper on Just in time summoning of unikernels (Jitsu). It's exactly what you describe — http://unikernel.org/files/2015-nsdi-jitsu.pdf http://unikernel.org/files/2015-nsdi-jitsu.pdf There's also some speculative stuff I wrote last year about demand-driven clouds (before I heard of 'serverless') — http://amirchaudhry.com/heroku-for-unikernels-pt2 http://amirchaudhry.com/heroku-for-unikernels-pt2