One Server, Three Languages

Learn C, Go and Rust by building the same server three times

  • C17 · Go 1.27 · Rust 1.99
  • One server, built three times
  • 70 exercises with solutions
  • 101-row scorecard
  • Part V: Rust from first principles
  • Part VI: kernels and drivers

Build one Redis-compatible server in C, Go and Rust, and learn when to choose each. Then go under it, to a small kernel and a driver in C and Rust.

Read online

Computer Networks: The Sorting Office

Eighty years of networks, told through one Friday outage

  • ARPANET to Kubernetes
  • AWS and Azure names
  • 125 named traps
  • 69 diagrams
  • No code, no labs

Follow one weekend outage layer by layer, with the history of why each piece exists.

Read online

Maintainable Playwright Tests

Data-driven, DRY, multi-locale end-to-end tests with TypeScript

  • Playwright 1.63 · TypeScript 7
  • en-GB · en-US · de-DE · ja-JP
  • 43 named traps
  • 15 diagrams
  • Every snippet type-checked

Rebuild a multi-market insurance quote suite the Playwright way, one broken test at a time.

Read online

Cybersecurity: The Keep

How each security control works, from the wax seal to AI

  • Ciphers to zero trust and AI
  • Microsoft · AWS · Google · IBM
  • 204 named traps
  • 37 diagrams
  • Laptop-only demos

Secure one small savings app, from its first leaked spreadsheet to a weekend incident response.

Read online

DDD and Microservices: The Atlas

Domain-driven design and microservices, with their traps

  • DDD · hexagonal · CQRS · sagas
  • Java 21 snippets
  • 114 named traps
  • 30 diagrams
  • Second edition

Split a monolith badly, then draw the right borders with DDD, events and sagas.

Read online

System Design: The Depot

Scaling, data and staying up under real load

  • Scale · data · reliability
  • Java 21 and SQL snippets
  • 91 named traps
  • 31 diagrams
  • One set of numbers throughout

Take one online shop from quiet to half a million users at 09:00, with numbers.

Read online

Software Architecture: The Town Plan

Choosing an architecture and keeping it true

  • Nine styles compared
  • Decision records · C4 · fitness functions
  • 69 named traps
  • 37 diagrams
  • Java 21 snippets

Choose an architecture for an inherited system, record the decisions, and keep them true.

Read online

From Docker to Kubernetes

A short story from one container to a self-running cluster, with the commands that matter

  • Docker 27 · Kubernetes 1.37
  • Helm · Istio · Prometheus · Argo CD
  • 55 diagrams · 60 gotchas
  • New: two deep manuals
  • ⌘K search

Ship one small app from a single container to a self-running cluster.

Read online

AWS for Azure Architects and Developers

Design enterprise AWS systems end to end, whatever you know of Azure

  • AWS as of September 2026
  • Terraform 1.16 · Java 25
  • 125 figures with official icons

Learn AWS on its own terms, with Azure as a bridge, through one payments platform.

Read online

GOV.UK Stack, Fast

Nunjucks, Express and Fastify, GOV.UK Frontend and CASA for React and .NET developers

  • GOV.UK Frontend 6.5
  • Express 5 · Fastify 5
  • CASA 10, optional

Map what you know from React and .NET onto a UK government service stack.

Read online

GitLab CI/CD, Decoded

Write, read and fix your team's pipeline, from commit to cluster

  • GitLab 19.3
  • Handbook in an hour
  • Node, Java and OpenTofu labs
  • Flux and Argo CD
  • AWS and Azure

Read, write and fix any GitLab pipeline: a one-hour handbook plus a full textbook.

Read online

Java for C# Developers

A working handbook for .NET engineers moving to Java and Spring Boot

  • Java 25 LTS
  • .NET 10 · C# 14
  • Spring Boot 3 & 4
  • Sibling: The Order Service, in depth

Where your C# instincts carry over to Java, and where they are confidently wrong.

Read online

The Order Service: Java and Spring Boot in depth

One DDD microservice, every mechanism explained, for C# developers

  • Spring Boot 4.1 · Java 25
  • One order service, 36 chapters
  • 164 design questions, answered from 19 principles
  • Companion code, built and tested

Build one DDD order service in Spring Boot, and understand every mechanism it relies on. Then drill the design questions experienced teams ask, each answered from a principle.

Read online