Where Next?
You have a running app: a module, a provider, a controller. Everything past this point is the same move — add a package, add one namespace key to your module config, and write a plain class the compiler wires for you. This page is the map: find the goal you have next, and it points you at the package, the guide, and a runnable example that proves it.
Real product
The things almost every API needs, in roughly the order you'll reach for them.
| I want to… | Package(s) | Guide | Proven by |
|---|---|---|---|
| Split a feature behind its own module | runtime | Modules | L01-minimal |
| Validate a request body | schema | Validation & DTOs | L02-http-validation |
| Define an API once for server and client | contract + client | Contracts | openapi-mcp |
| Persist real data | drizzle | Drizzle | L04-database |
| Protect endpoints | auth | Authentication | L07-auth |
| Test a module end-to-end | testing | Testing Guide | L01-minimal |
| Turn framework failures into consistent JSON errors | runtime | Error Handling | L02-http-validation |
| Structure logs and trace a request | logging | Logging & Observability | L01-minimal |
Production concerns
Operational needs — nothing here changes your architecture, it just makes the app production-grade.
| I want to… | Package(s) | Guide | Proven by |
|---|---|---|---|
| Decouple modules with events | events | Events | L03-events |
| Run work off the request path | queue | Queue & Messaging | L08-queue |
| Run work on a schedule | schedule | Scheduled Work | edge-platforms |
| Cache reads | cache | Caching | flagship |
| Store simple key/value data or files | kv · blob | Key/Value Storage, Blob Storage | storage-blob-adapters |
| Expose health and readiness probes | health | Health & Readiness | flagship |
| Make a retried write or event safe to run twice | (idempotency subpaths) | Idempotency | flagship |
| Send email, SMS, or push notifications | notifications | Notifications | notifications |
Architecture at scale
| I want to… | Package(s) | Guide | Proven by |
|---|---|---|---|
| Split writes from reads | cqrs | CQRS | L05-cqrs |
| Model a domain with invariants | domain | Domain-Driven Design | L06-ddd |
| Publish events reliably across services | integration | Integration Events | flagship |
| Coordinate a multi-step process with a deadline | saga | Saga Orchestration | saga-orchestration |
| Write a durable, resumable procedure | workflow | Durable Workflows | flagship |
| Fan one event out to several independent services | queue (cross-service transports) | Integration Events | cross-service-transports |
Platform superpowers
Real-time transports, tracing, and per-platform deploys — the same modules, running unchanged.
| I want to… | Package(s) | Guide | Proven by |
|---|---|---|---|
| Push updates to a connected client | websocket · sse | WebSockets, Server-Sent Events | flagship's apps/cloudflare |
| Hold state across messages on the edge | durable | Durable Objects | flagship's apps/cloudflare |
| Get typed clients for WebSockets and SSE | client | Typed Clients | flagship's packages/realtime |
| Trace requests with OpenTelemetry | otel | Observability & Tracing | edge-platforms |
| Deploy to Cloudflare, Vercel, Netlify, AWS, or Deno | nitro · node · cloudflare · vercel · netlify · aws · deno | Deploy targets | nitro-presets |
| Ship an OpenAPI doc or an MCP tool surface from a contract | openapi · mcp | OpenAPI, MCP Server | openapi-mcp |
The full runnable catalog — every ladder step, the flagship monorepo, and every gap example — lives on the Examples page. Clone one, run pnpm dev, and read the source alongside whichever guide you picked above.
Examples
Runnable examples in three tiers — a progressive learning ladder (L01–L08), the event-ticketing flagship monorepo, and thematic gap examples for platform and feature one-offs.
Troubleshooting
Fixes for the common first-run issues — missing routes, unresolved dependencies, validation 400s, a hanging middleware, a failed build after an edit — plus deeper diagnostics for contracts, scopes, and context.