So you can map this onto your own stack: for HTTP and views, axum for the router and
handlers, maud for compile-time-checked HTML, tower /
tower-http for the middleware stack. The async runtime is
tokio, multi-threaded, with signal handling for graceful shutdown. The database is
sea-orm over Postgres with sea-orm-migration for
schema, and uuid (v7) + chrono for keys and timestamps. Durable
execution is restate-sdk hosting every workflow on one worker endpoint, with the
journal doing the remembering. The archive uses arrow +
parquet to turn the nightly Postgres snapshot into open columnar files. Content is
pulldown-cmark, which renders the very markdown you are reading right now. Cloud
is google-cloud-storage behind a storage trait, with
reqwest for the REST plumbing that provisions a fresh project. Identity is
jsonwebtoken and oauth2 for the OIDC flow. Tests use
testcontainers for a real Postgres per test binary,
fantoccini to drive a real browser over WebDriver, and
cucumber for the behavior specs you saw in Step 2. One workspace, one cargo test, one
language from the HTTP handler down to the migration and back up to the browser assertion. None of these crates asked us
to sign anything.