Appendix: Reference Books
This course is grounded in a handful of books. Where a chapter anchors a concept to a specific book, it cites it inline. This appendix says what each one is for, so you know where to go deeper. This is the third Panoptes course, so it leans on the same canon as the first two and adds the definitive reference for building a production Rust service.
Zero to Production in Rust — Luca Palmieri
The primary source for Parts IV–VII (persistence, the service, the scheduler, telemetry). Its framework-agnostic chapters are the backbone of this course's service arc: sqlx with a connection pool and migrations, structured tracing (spans, the subscriber, request-scoped instrumentation), error handling that maps cleanly to HTTP status codes, and — most importantly for a control plane — idempotency and at-least-once delivery. The book builds on actix-web; this course uses axum instead, so we take the reasoning (why a pool, why spans, why idempotency keys) and not the framework specifics. When a design decision in the coordinator has a "because Palmieri showed why," this is the citation.
Rust for Rustaceans — Jon Gjengset (No Starch)
The reference for the seam and the trait objects that carry it. Its chapters on trait objects, dyn dispatch, Send/Sync, and API design inform the WorkerHandle/ModelClient seams and the connection-actor design in Part VIII. This is the book to open when a lifetime or an Arc<dyn Trait> bound surprises you.
Async Rust — Maxwell Flitton & Caroline Morton (O'Reilly)
The source for the concurrency and networking mechanics. Its treatment of the future lifecycle, the runtime's polling loop, select!, channels, and cancellation underpins the scheduler's bounded concurrency (Part VI) and the connection actor multiplexing one socket (Part VIII). If any async idea in this course feels thin — especially tokio::select! with a bias, or why a dropped receiver cancels a send — this is the book to open.
Command-Line Rust — Ken Youens-Clark (O'Reilly)
The reference for the two binaries. Both panoptes-control and panoptes-worker are clap programs with honest exit behavior and integration tests that run the compiled binary. Its discipline around composability and exit codes is what makes the coordinator and worker feel like tools rather than scripts.
Effective Rust — David Drysdale (O'Reilly)
A best-practices reference, organized as numbered "items." Consulted for idiomatic choices around the type system, error handling (thiserror vs anyhow, the #[from] conversion), and API design. Where a design decision has an idiomatic "right answer," this book usually has an item on it.
AI Engineering — Chip Huyen (O'Reilly)
Foundational knowledge for the evaluation methodology the control plane serves. It frames why an eval harness schedules many model calls across epochs, why token and cost accounting matter, and what the execute stage is producing inputs for. Read it to keep the why of the whole system in view while you build its plumbing.