ENTER

THE UNIKERNEL

Cool things about that...

Fast boot
Optimized
Tiny footprint
Lower attack surface area
12-factor-app-ness

The Twelve Factors

One codebase tracked in revision control, many deploys
Explicitly declare and isolate dependencies
Store config in the environment
Treat backing services as attached resources
Strictly separate build and run stages
Execute the app as one or more stateless processes
Export services via port binding
Scale out via the process model
Maximize robustness with fast startup and graceful shutdown
Keep development, staging, and production as similar as possible
Treat logs as event streams
Run admin/management tasks as one-off processes

Erlang on Xen

#include <os>
#include <net/inet4>
#include <math.h>
#include <iostream>
#include <sstream>
#include <net/dhcp/dh4client.hpp>

using namespace std::chrono;

std::unique_ptr<net::Inet4<VirtioNet> > inet;

void Service::start() {
  Nic<VirtioNet>& eth0 = Dev::eth<0,VirtioNet>();  
  inet = std::make_unique<net::Inet4<VirtioNet> >(eth0);
  inet->network_config( {{ 10,0,0,42 }},      // IP
			{{ 255,255,255,0 }},  // Netmask
			{{ 10,0,0,1 }},       // Gateway
			{{ 8,8,8,8 }} );      // DNS

runtime.js

var runtime = require('runtimejs')
console.log('Hello world!')

# install dependencies
npm install runtimejs
npm install runtimeify -g
npm install runtime-tools -g

# bundle up ramdisk image
runtimeify index.js -o initrd

# make sure you have QEMU installed
brew install qemu           # OSX
sudo apt-get install qemu   # Ubuntu

# run it in QEMU
runtime-qemu ./initr

Rump Kernels

NetBSD Drivers: build the software stack you need without forcing you to reinvent the wheels
Only a few thousand lines of glue, plus rump kernel components
Runs on Xen, KVM, and bare metal.
Packages!