A

autochitect

Explore software architecture ◆

Explore the Stack

Click any component to explore how it works. The Ethernet cable connects the two computers.

💻 Computer AClient
Motherboard
CPU
±ALU
Control Unit
RAM
NIC
λOS
Peripherals
💻 Computer BServer
Motherboard
CPU
±ALU
Control Unit
RAM
NIC
λOS
Peripherals

Recent Write-ups

Storage Durability

2026-05-22System DesignStorageDatabasesDistributed Systems

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 →

Replication

2026-05-22System DesignDistributed SystemsConsistency

How distributed systems copy data across multiple nodes to survive failures, scale reads, and reduce latency.

Read write-up →

Memory Allocators

2026-05-22InternalsRuntimeMemoryPerformanceSystems

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 →

Leader Election

2026-05-22System DesignDistributed SystemsConsensus

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 →

Just-In-Time (JIT) Compilation

2026-05-22CompilersPerformanceSystems Programming

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 →

HTTP/2 & HTTP/3

2026-05-22NetworkingProtocolsPerformanceArchitecture

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 →

Garbage Collection

2026-05-22InternalsRuntimeMemoryPerformance

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 →

TCP/IP 4-Layer Model

2026-05-12NetworkingProtocolsFundamentalsArchitecture

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 →

OSI Model

2026-05-12NetworkingProtocolsFundamentals

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 →

Gossip Protocol

2026-05-11System DesignDistributed SystemsConsistency

How nodes in a distributed system spread information reliably using epidemic-style peer-to-peer communication.

Read write-up →

Backpressure

2026-04-20System DesignStreamingResilience

How producers and consumers negotiate throughput so that a fast upstream never overwhelms a slow downstream.

Read write-up →

Raft Protocol

2026-04-10System DesignDistributed SystemsConsensus

How Raft achieves distributed consensus with leader election and log replication, making it the readable alternative to Paxos.

Read write-up →