vtex-io-service-runtime

To define and register routes for a VTEX IO backend service, implement the runtime entry point at node/index.ts and configure the explicit route exposure in service.json.

A correct VTEX IO service runtime structure separates node/index.ts as the runtime composition root from domain modules, keeping business logic out of the runtime wiring.

Configure runtime knobs like memory, timeout, ttl, and replicas in VTEX IO by defining them explicitly within the service.json configuration file.

Enforcing a typed Context and State for VTEX IO service handlers ensures a strict runtime contract, preventing the mixing of runtime wiring with business logic.

Yes, you can register GraphQL handlers and events in a VTEX IO service by explicitly exposing them in the runtime surface defined by your service configuration.

The best way to separate business logic from runtime wiring in VTEX IO is to use node/index.ts strictly as a runtime composition root and place domain logic in separate modules.