Learn the why.
Master the how.

The library we train our own engineers with — from senior to principal. Published as we finish it, written to the same production standard as everything else we ship.

Go from Zero to Production BOOK Go Concurrency COURSE Distributed Computing Foundations Distributed Infrastructure in Go Production Distributed Systems
labs › catalog

The Library

The full syllabus of every title is published before launch — the same way our case studies publish the ADRs. What you see below is the actual table of contents, with honest build status.

labs/go-concurrency/book.md ● 22/22 BUILT
BOOK

Go Concurrency: From Fundamentals to Production

Correct mental models first — goroutines, channels, select — then channel mastery, shared state and the memory model, context and cancellation, and the production discipline: testing, debugging, and performance, down to the GMP scheduler.

progress › all 22 built
labs/distributed-systems/course-1-foundations.md ◐ IN DEVELOPMENT · 4/22 BUILT
COURSE · 1 OF 3

Distributed Computing Foundations in Go

The first course of the Distributed Systems in Go series — the bridge from concurrent to distributed. Real networking, wire protocols, serialization, RPC and gRPC, time and causality, failure detection — closing with a build project: a distributed key-value store, v1.

progress › 4 built · 1 in draft · 17 queued · all 22 mapped
syllabus › all 22 chapters mapped · ✓ = built
part 1 › the distributed mindset
01from concurrent to distributed
02networks, failures & the eight fallacies
03failure models & the distribution decision
part 2 › networking in go
04tcp networking in go
05connection managementdraft
06building wire protocolsqueued
07http & http/2 in goqueued
08transport security — tls & mtlsqueued
part 3 › serialization & data exchange
09serialization fundamentalsqueued
10protocol buffers in goqueued
11schema evolution & compatibilityqueued
part 4 › remote procedure calls
12rpc concepts & semanticsqueued
13an rpc framework from scratchqueued
14grpc in goqueued
15api design for distributed servicesqueued
part 5 › time, order & causality
16physical time & its limitationsqueued
17logical clocksqueued
18hybrid logical clocksqueued
part 6 › failure detection & resilience
19failure detectionqueued
20timeouts & retriesqueued
21idempotency & safe operationsqueued
22circuit breakers & partial failurequeued
build project
kvdistributed key-value store — v1queued

Go from Zero to Production

○ BOOK · QUEUED

The on-ramp — the Go language itself, taught to the same depth as everything here. The natural first read, before the concurrency book.

Distributed Infrastructure in Go

○ COURSE 2 · MAPPED

Consistency and replication, consensus, partitioning, distributed transactions, storage, and event systems — the machinery under every reliable platform.

Production Distributed Systems in Go

○ COURSE 3 · MAPPED

Service architecture, reliability engineering, testing, observability, multi-region, and workflow orchestration — running distributed systems for real.

labs › routing

Where do I start?

The library tells one story. The books make you dangerous on a single machine; the courses take you across the network — where every guarantee you relied on stops holding.

ONE MACHINE
Go from Zero to Production
the language · types · interfaces · tooling
○ book · queued · the on-ramp
Go Concurrency
goroutines · channels · one process
● 22/22 built · start here
MANY MACHINES
Distributed Computing Foundations
sockets · rpc · time · failure
◐ in development · course 1
Distributed Infrastructure
replication · consensus · sharding
○ course 2 · mapped
Production Distributed Systems
reliability · multi-region · operations
○ course 3 · mapped
everything left of the line is one process — everything right of it is the hard part
# fallacy 01 › "the network is reliable" — the courses begin where it stops being true
notify ›

One email when a title ships.

No drip campaign, no newsletter — one email per release, nothing else.

✓ subscribed — one email when a title ships
something broke — email us instead: contact@corebackend.dev