Beej's Guide to Network Programming (beej.us) · Brian "Beej" Hall
The sockets API every server is built on, including the partial sends that bite real programs.
Plans / Plan 03 · Three months
The backend under your framework
You end up withYou can explain what happens between a request arriving on a socket and a row being committed, and what breaks when there's more than one server.
- Three months
- 6 steps
- from 4 courses
- 7,872 points
The steps
Implement DNS in a Weekend (implement-dns.wizardzines.com) · Julia Evans
The lookup before every connection, built as a resolver you can watch.
Build Your Own Redis with C/C++ (build-your-own.org) · James Smith
A Redis-like server on top of those sockets: an event loop, a hashtable, sorted sets, TTLs. The shape of most caches and many servers.
Let's Build a Simple Database (a SQLite clone in C) (cstack.github.io) · Connor Stack
A storage engine: a pager and an on-disk B-tree, the structure behind most database indexes.
How Postgres Makes Transactions Atomic (brandur.org) · Brandur Leach
How a real database makes a transaction atomic, followed through the Postgres source.
Gossip Glomers, on Maelstrom (fly.io) · Fly.io and Kyle Kingsbury
Nodes that Maelstrom breaks with partitions and delays. It's the bridge from one server to several.
What this plan leaves out
TLS (the networking course's Stage 4) and the full database books. The first is in the security plan; the second is the databases course itself.
After this
The databases course from step 6, or the distributed systems course from step 2 (Raft).