vtex-io-service-runtime

Structure VTEX IO Node services by using `node/index.ts` as the composition root to wire clients and register runtime surfaces like routes and events. Keep business logic out of the entrypoint and move execution behavior into `service.json`.

The `service.json` contract in VTEX IO defines explicit platform execution configuration. It sets runtime knobs for timeouts, ttl, workers, replicas, rate limiting, and intentionally declares route or event exposure including `public` and `smartcache` settings.

Configure VTEX IO backend app scaling and timeouts by defining explicit execution settings in `service.json`. Adjust runtime knobs for memory, replicas, workers, and rate limiting to resolve intermittent execution-model failures and poor scaling behavior.

Set up typed Context and State contracts for VTEX IO handlers by establishing type-safe contracts so middleware and handlers share `ctx.state`, `ctx.vtex`, and params safely. This avoids falling back to `any` when composing routes, events, and GraphQL handlers.

VTEX IO node services intermittently time out or scale poorly when business logic mixes into the Service entrypoint and execution settings remain unclear. Restructure the entrypoint, move execution behavior into `service.json`, and verify routes are registered through the runtime layer.

Yes, you can compose GraphQL handlers with typed Context in a VTEX IO runtime service. Register GraphQL handlers through the runtime composition layer in `node/index.ts` while using type-safe contracts for `ctx.state` and `ctx.vtex` to ensure safe parameter sharing.