vtex-io-data-access-patterns

Select data storage patterns for VTEX IO apps with caching and ownership guidance.

39|9|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/vtex/ai-skills --skill vtex-io-data-access-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vtex-io-data-access-patterns
Source: https://github.com/vtex/ai-skills/tree/main/tracks/vtex-io/skills/vtex-io-data-access-patterns
Command: npx skills add https://github.com/vtex/ai-skills --skill vtex-io-data-access-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Data Access & Storage Patterns skill guides VTEX IO developers in deciding where data should reside and how to access it, to avoid duplicated sources of truth and misaligned data ownership.

Core Features & Use Cases

  • Guidance on selecting the appropriate data storage home (Master Data, VBase, app settings, core APIs, or external stores) for VTEX IO apps.
  • Rules for designing reads, writes, cache strategies, and deriving views to minimize data duplication.
  • Use case examples for data-heavy apps, configuration flows, and lifecycle management of stored data.

Quick Start

Ask for guidance on selecting a storage pattern for a VTEX IO app and how to implement it.

Frequently Asked Questions about vtex-io-data-access-patterns

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

FAQPage Schema
Where should I store data in a VTEX IO app to avoid duplicating the source of truth?

Data storage in VTEX IO should use a single source of truth by selecting the right home—Master Data, VBase, app settings, core APIs, or external stores—based on ownership and read/write patterns to prevent duplication.

When should I use VBase instead of Master Data for my VTEX IO application?

VBase suits app-specific or ephemeral data, while Master Data serves as the source of truth for shared business records; choosing correctly ensures proper data ownership and minimizes misaligned access patterns.

How do I design an effective caching strategy for data access patterns in VTEX IO?

Design caching in VTEX IO by deriving views from the source of truth, applying rules for when to cache reads, and reviewing risks to ensure data consistency and performance across data flows.

What are the limitations of storing configuration data directly in app settings on VTEX IO?

App settings in VTEX IO are limited to static configuration; they lack the dynamic query, lifecycle management, and write capabilities needed for data-heavy apps, making them unsuitable as a primary data store.

Can I use an external store as the source of truth for a VTEX IO app?

Yes, external stores can serve as the source of truth for VTEX IO apps when integrated correctly, provided you follow explicit recommendations on data flows, querying, and caching to maintain performance.