vtex-io-masterdata-strategy

Use Master Data v2 for custom data in VTEX IO apps when you need structured entity boundaries, schema lifecycle management, and indexed field filtering. It evaluates your specific data storage needs to determine if Master Data is the appropriate mechanism over alternative storage approaches.

Manage schema lifecycle in Master Data v2 by planning schema ownership, validation rules, and evolution strategies. This approach prevents schema sprawl by defining clear boundaries for entity data structures and controlling how schemas change throughout the application lifecycle.

Master Data v2 supports custom indexing by allowing you to index only relevant fields for efficient filtering and search. This targeted indexing strategy optimizes query performance within your VTEX IO applications without unnecessary overhead on non-critical data fields.

The best way to define entity boundaries for VTEX IO custom data is to evaluate your application's specific data structures against Master Data v2 capabilities. This ensures proper separation of concerns for reviews, wishlists, or forms, maintaining clean data architecture.

You should not use Master Data v2 when your custom data requirements fall outside its schema lifecycle and indexing capabilities. Compare Master Data with alternative storage mechanisms to determine if another approach better suits your specific application data patterns.