Busca en todas las páginas de la documentación
Engineering roadmap input translates Rust reality into planning language: edition cliffs, reliability investments, and platform work that unlocks product bets. A quarterly one-pager beats surprise "we need a month for toolchain" mid-quarter.
Quick-reference recipe card - copy-paste ready.
# Engineering input Q3 (orders platform)
## Outcomes we enable
- EU launch (GDPR export path, audit logging)
- 99.9% checkout SLO (pool + tracing investment)
## Investments requested (20% capacity)
1. sqlx migration expand phase - blocks EU schema
2. cargo-vet + SBOM - enterprise deal #442
3. Worker/API deploy coupling automation - CFR reduction
## Defer with trigger
- Workspace split into 5 binaries - revisit when team >= 12
## Risks if ignored
- Edition 2024 drift blocks hiring playbook
- INC-9011 recurrence on pool configWhen to reach for this:
| Roadmap row (product language) | Engineering work | Size |
|--------------------------------|------------------|------|
| Faster invoice export | Polars lazy pipeline + worker memory caps | M |
| Enterprise security questionnaire | cargo-audit, vet, SBOM in CI | S |
| Reduce checkout incidents | sqlx pool alerts + runbook (post INC-8812) | S |PM owns priority order; engineering owns feasibility and dependency links.
DORA trends, top incidents, support themes, security audit gaps, compile CI duration, hiring/onboarding friction.
| Alternative | Use When | Don't Use When |
|---|---|---|
| OKRs linking eng KPIs | Mature planning | Team <5 without OKR culture |
| Tech radar slide | Educate leadership on Rust ecosystem | Sole planning artifact |
| RFC portfolio review | Many parallel migrations | Simple single-service squad |
| Joint eng/product roadmap doc | Strong partnership | Weak PM engagement |
Three bullets: outcome, risk $, capacity % - appendix for engineers.
EM + tech lead together; PM owns business priority narrative.
Roadmap themes; backlog tickets execute - link each theme to epics.
Yes with trade-off explicit: what drops if new item enters.
Central platform roadmap + squad overlays for product-specific work.
Yes if Rust hiring is bottleneck for roadmap commitments.
Flag as fixed-date; engineering marks dependency risks early.
Include if product depends on crate releases; security tie-in.
Compare planned vs delivered outcomes quarterly; not story points vanity.
Feasibility veto with alternatives and dates - document in one-pager.
Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.
Revisado por Chris St. John·Última actualización: 16 jul 2026