Why I Chose vsock Over TCP for a Firecracker Serverless Runtime
2h ago· 1 min readNews
Why I Chose vsock Over TCP for a Firecracker Serverless Runtime
When building a Firecracker-based serverless platform, vsock is preferred over TCP/IP for communication between the host and microVMs because it reduces latency and overhead on the hot invocation path.
#hackernews #news
You might also wanna read
Implementing High-Performance VM Communication with Linux vsock and gRPC
This technical article explains how to use Linux vsock (virtual sockets) for fast communication between virtual machines and host systems, b
popovicu.com·6mo ago
Optimizing Linux timestamps on x86: 30% faster custom timers without vDSO
A deep technical exploration of optimizing Linux timestamps on x86 architecture, achieving 30% speed improvements over standard system clock
hmpcabral.com·1mo agoThe transactional outbox pattern: keeping a database and Kafka consistent
medium.com·8d ago
The Case for Using Single Server Architecture Over Distributed Systems
The article argues against the trend of distributed systems and microservices, advocating instead for using "one big server" when possible.
specbranch.com·9mo agoEvolution of High-Performance Web Servers: From C10k to io_uring, kTLS and Rust
This article discusses the evolution of high-performance web servers, focusing on the historical context of the C10k problem and the progres
blog.habets.se·9mo ago
Why Python Cannot Be Sandboxed and Alternative Approaches: Firecracker, gVisor, and WASM
This article examines the fundamental challenges of sandboxing Python code and compares different sandboxing approaches. It explains why Pyt
gist.github.com·5mo ago