vtex-io-application-performance

Apply caching, deduplication, and parallel execution to VTEX IO Node or .NET resolvers.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/exilonX/ap2 --skill vtex-io-application-performance-exilonx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vtex-io-application-performance
Source: https://github.com/exilonX/ap2/tree/main/.agents/skills/vtex-io-application-performance
Command: npx skills add https://github.com/exilonX/ap2 --skill vtex-io-application-performance-exilonx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reduce latency and improve resilience in VTEX IO backends by applying production-ready application-level caching, deduplication, and parallelization patterns instead of relying only on edge caching.

Core Features & Use Cases

  • Multi-layer caching: Use bounded in-process LRU for fast hot reads, optionally backed by shared VBase with stale-while-revalidate for lower tail latency.
  • Request-safe deduplication: Prevent duplicate upstream calls within a resolver chain using ctx.state flags and explicit client/context wiring (e.g., ctx.clients).
  • Performance-safe execution: Parallelize independent upstream calls with phased Promise.all and enforce explicit timeouts and graceful degradation for reliability.
  • Correctness guardrails: Avoid caching transactional real-time data (order forms, cart simulations, payment responses) and apply strict constraints for idempotency-critical VBase writes.

Quick Start

Use vtex-io-application-performance to audit your VTEX IO resolvers and refactor hot-path logic to add tenant-scoped LRU/VBase caching for reference data, parallelize independent client calls, and ensure timeouts and non-cached transactional data are enforced.

Frequently Asked Questions about vtex-io-application-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve VTEX IO backend latency and resilience?▼

Improve VTEX IO backend latency by applying application-level caching, request deduplication, and parallel execution patterns instead of relying solely on edge caching for reference data.

Can I use stale-while-revalidate with VBase for caching in VTEX IO?▼

Yes, you can back bounded in-process LRU caches with shared VBase using stale-while-revalidate patterns to achieve lower tail latency across your VTEX IO services.

What is the best way to prevent duplicate upstream calls in VTEX IO resolvers?▼

Prevent duplicate upstream calls within a resolver chain by implementing request-safe deduplication using ctx.state flags and explicit client or context wiring.

How do I parallelize independent upstream calls in a VTEX IO Node service?▼

Parallelize independent upstream calls in VTEX IO Node services by using phased Promise.all execution while enforcing explicit outbound timeouts and graceful degradation.

When should I avoid application-level caching in VTEX IO?▼

Avoid application-level caching for transactional real-time data like order forms, cart simulations, and payment responses, applying strict constraints for idempotency-critical VBase writes.