vtex-io-service-apps

Build a VTEX IO backend by defining a Service entry point, wiring REST routes, GraphQL resolvers, and event handlers, then registering typed IOClients to ensure per-request context, caching, and metrics.

The best way to structure VTEX IO apps is using a service-first architecture that wires routes, GraphQL resolvers, and events in a single typed service while keeping business logic separate from client implementations.

A Service entry point handles per-request context and caching by using the @vtex/api clients registry, exposing clients via ctx.clients to manage lifecycles and built-in features automatically.

Yes, you need @vtex/api to create custom IOClients for Master Data access, as it enforces proper client lifecycles and provides the built-in features required for secure data handling.

Yes, you can wire middleware and GraphQL resolvers in a single VTEX IO backend service by applying a service-first architecture that centralizes these common patterns within one typed application.

Separate business logic from clients when developing VTEX IO backend services to enforce best-practices, ensure proper client lifecycles, and maintain clear guidelines for routes, resolvers, and events.