3 ms·
I'm thinking of simplicity. No VMs, no containers, just a single binary. The majority of microservices I've written would fit into a system like this just fine
by com2kid 7y ago
I'm thinking of simplicity. No VMs, no containers, just a single binary.
The majority of microservices I've written would fit into a system like this just fine.
NodeJS is built around the idea that a single thread of execution is enough for a stupidly large % of backend code. On top of that is ton of infrastructure to deploy slews of 100 line JS microservices that each do one thing.
So, back to basics. No VM, no disk at runtime, a single statically linked binary running on top of nearly bare metal.
Available memory is whatever space the program code doesn't take up.
Ignoring l3 being unaddressable, I wonder if UEFI applications are powerful enough to pull something like image deployment off.
This is probably all less efficient than the current Russian doll system of VMs and containers in use right now, but it is fun to imagine!
- wmf 7y agoBasically unikernels on the Jailhouse hypervisor.
- londons_explore 7y ago> Ignoring l3 being unaddressable If you set the right config registers, you can map the cache to a linear address space and use it like RAM. I think to do that, you loose access to actual RAM though, so it isn't awfully practical.