Storage Durability
How databases and filesystems guarantee that committed writes survive crashes — from fsync and write-ahead logs to the hardware tricks that make them work.
Read write-up →autochitect
Explore software architecture ◆
Click any component to explore how it works. The Ethernet cable connects the two computers.
How databases and filesystems guarantee that committed writes survive crashes — from fsync and write-ahead logs to the hardware tricks that make them work.
Read write-up →How distributed systems copy data across multiple nodes to survive failures, scale reads, and reduce latency.
Read write-up →How allocators carve up heap memory, the algorithms behind malloc and modern arenas, and why TigerBeetle's fixed-memory model eliminates allocation entirely.
Read write-up →How distributed systems agree on a single coordinator — the algorithms, failure modes, and trade-offs of electing a leader without a central authority.
Read write-up →How JIT compilers generate native machine code at runtime — from mmap and PROT_EXEC to a recursive codegen that walks an AST and emits real x86-64 instructions.
Read write-up →How HTTP evolved from a text protocol with one request per connection to a multiplexed binary stream, and then to a transport built on UDP that survives network switches.
Read write-up →How runtimes automatically reclaim memory, the algorithmic trade-offs between throughput and pause time, and why GC behavior should shape your service architecture.
Read write-up →The network model that actually shipped. How four layers — Link, Internet, Transport, Application — carry every byte your services send, and why every architecture decision you make is secretly a layer decision.
Read write-up →What a socket actually is, how the OS manages the full lifecycle of a connection, why unmanaged sockets drain CPU at scale, and how DNS prefetch and stale cache interact with socket behaviour.
Read write-up →How decomposing network communication into seven independent layers solved vendor lock-in and became the mental model every engineer still reaches for.
Read write-up →How nodes in a distributed system spread information reliably using epidemic-style peer-to-peer communication.
Read write-up →How producers and consumers negotiate throughput so that a fast upstream never overwhelms a slow downstream.
Read write-up →How Raft achieves distributed consensus with leader election and log replication, making it the readable alternative to Paxos.
Read write-up →