FTL: A new operating system for clouds
FTL is a new cloud operating system and kernel that implements OS features as a shared userspace library, offering Linux binary compatibility with enhanced container isolation.
summary is enough The landing page provides a high-level architectural overview of a novel userspace OS design, which can be grasped quickly without deep-diving.
summary
FTL introduces a cloud-oriented operating system architecture where core OS services run as shared userspace libraries atop a minimal kernel. It targets hypervisor-like hardware isolation while keeping full compatibility with standard Linux binaries. By bridging microkernel security principles with monolithic performance, it aims to make lightweight containers as secure as full virtual machines. The recently released v0.1.0 adds asynchronous Rust support and expands its Linux compatibility layer.
key points
- FTL structures the operating system as a userspace library, allowing OS features to be developed, debugged, and upgraded like regular applications.
- The minimal FTL kernel isolates containers using a hypervisor-like user-mode interface rather than running heavy bare-metal virtualization.
- It supports unmodified Linux binaries and specialized workloads, such as a multi-threaded Tokio-based HTTP server written in Rust.
who should read it
Systems engineers and cloud architects interested in alternative kernel designs, container isolation, and unikernel-like architectures.
discussion positive
consensus
Participants find the architecture intriguing, comparing FTL to gVisor, exokernels, and unikernels while debating its approach to traditional monolithic designs.
pushback
Some question how FTL handles complex hardware drivers and device models, arguing that bypassing standard Linux drivers shifts too much burden onto application developers.
It's a classic exokernel. Which unfortunately feels like there's some secret cabal paying those writing operating systems textbook writers to explain poorly.
Basically the point is rather than keeping the absolute minimum in the kernel, you keep the minimum needed to multiplex the hardware with the fewest abstractions possible. So stick a network driver in there, sure. But does the TCP stack need to be in there? Stick a disk driver in there, but does the VFS need to be in there?
Then you add security so that the fast path doesn't need to go to a user space abstraction service. You have …
It clarifies that FTL is a classic exokernel design rather than a traditional unikernel, explaining how hardware multiplexing and fast paths work.
Generated by an LLM from the article and thread. Check the sources before relying on it.