Rust Systems & Async Engineering Bootcamp Certificate

Checkpoint 1: Build a Rust CLI or networked service with Cargo workspaces/modules, typed configuration and explicit Result-based error propagation rather than panic-driven control flow.
Checkpoint 2: Design ownership and borrowing so data moves or borrows intentionally; remove unnecessary clones and document the lifetime/ownership model for the main data path.
Checkpoint 3: Use enums and pattern matching to model states and failures; demonstrate exhaustive handling and replace nullable/sentinel behavior with Option/Result where appropriate.
Checkpoint 4: Create reusable generic behavior with traits; compare static dispatch with a trait-object boundary where runtime polymorphism is justified and explain the tradeoff.
Checkpoint 5: Write iterator/closure-based transformations and test them against imperative equivalents for readability, allocation behavior and correctness.
Checkpoint 6: Add Tokio async I/O with cancellation/timeouts and bounded concurrency; instrument latency, reproduce one blocking or stalled path and fix it without hiding errors.

Day 1: Choose a systems workflow such as log processing, concurrent API aggregation or file/index service; define inputs, failure modes, latency targets and
Day 2: Build the synchronous baseline with structs/enums, Result/Option, modules and tests; draw the ownership/borrowing map for the critical data flow.
Day 3: Refactor clones and allocations, add trait-based abstractions and generic utilities, and document where lifetimes or owned values simplify the design.
Day 4: Add iterator/closure pipelines plus robust parsing/error propagation; test malformed, missing and boundary inputs without panics in normal failure paths.
Day 5: Introduce Tokio async I/O, timeouts and bounded task concurrency; compare synchronous and async behavior under a controlled workload.
Day 6: Inject a slow dependency, cancellation and partial failure; diagnose traces/metrics or timing evidence, remove accidental blocking and prove safe recovery.
Day 7: Publish repo, architecture/ownership diagram, test suite, error taxonomy, sync-vs-async benchmark, failure evidence, runbook and demo video.