Ch 01
Deployment posture
Stateless vs stateful as deployment posture — the same C++ binary, two state choices.
Reference
Excalidraw diagrams.
Architecture and flow diagrams for the statelessness compendium.
Click any diagram to open it fullscreen. Each is also available as
.excalidraw source — open it on
excalidraw.com
to edit.
Ch 02
RAII per-request scope
RequestContext as RAII per-request scope: ctor acquires, dtor releases on every exit.
Ch 03
PMR monotonic_buffer_resource
PMR monotonic_buffer_resource: bump-pointer per request, single bulk free at scope-end.
Ch 04
The state architecture table
The State Architecture Table: process-scoped, request-scoped, external — sort early.
Ch 05
Threading under cgroup limits
Threading in a cgroup-constrained service: cpu.max budgets the worker pool.
Ch 06
12-Factor adapted to C++
12-Factor adapted to C++: nine map directly, three collide (Config, Processes, Disposability).
Ch 07
State externalization
State externalization: process-scoped pool, ScopedConnection RAII, authoritative state outside the process.
Ch 07
The Outbox pattern
Outbox: order + event written in one transaction; a relay publishes with FOR UPDATE SKIP LOCKED; an idempotent consumer applies ON CONFLICT — at-least-once delivery plus idempotent apply = exactly-once effect.
Ch 08
The ephemeral filesystem trap
The ephemeral filesystem: overlayfs scratch + tmpfs vanish on restart, only PVCs persist, logs to stdout.
Ch 09
The three probes
Three probes (startup, liveness, readiness) and the graceful-shutdown sequence that ties scope destructors together.
Ch 09
Probe states and shutdown sequence
Health states (Starting → Serving ⇄ NotReady → Draining → Stopped) and the ordered SIGTERM shutdown sequence: flag, drain readiness, stop workers, Shutdown(deadline), reverse-order teardown, exit 0.
Ch 10
gRPC end-to-end example
gRPC end-to-end example: a complete order-pricing service composing process-, request-, and external-scope state.
Ch 11
Conan dev vs release profiles
Conan dev vs release profiles: same sources, same lockfile, two parallel build flows producing two binaries.