About Caching Data Query Results

Data caching significantly speeds up data queries. Wix automatically caches the results of certain data queries to a Content Delivery Network (CDN). When a visitor makes a query whose results are cached, Wix provides the cached results instead of querying the database again.

When does data caching occur?

Whether the results of a data query are cached depends on several factors.

Which data query results are cached?

Data query results are only cached when:

• The query does not make changes to the collection or to any of the items it contains.
• The queried collection is a native Wix Data collection.
• The query does not trigger any data hooks.
• The request is made by code that runs on the site frontend.
• The request is made on behalf of a site visitor.
• The request does not contain Personally Identifiable Information (PII).
• Eventual consistency is not overridden.
• The collection does not have item visibility enabled.

Which data request results are not cached?

Results of data requests are not cached when:

• The request modifies the collection or any of the items it contains, such as calls to insert() or remove().
• The data request is to a Wix app collection, an external collection, or to a shared collection.
• The request triggers a data hook.
• The request is made by code that runs on the site backend.
• The data request is made on behalf of a site member.
• The request contains Personally Identifiable Information (PII).
• Eventual consistency is overridden.
• The collection has item visibility enabled.

Data cache invalidation

Cache invalidation allows new, updated data to be cached and returned to visitors in future queries. The cache is automatically cleared when:

• A request makes changes to the collection or to any of its items. Any cached results that reference the modified collection are also cleared.
• The site is published.
• Results have been cached for one week or longer.

To make the best of Wix's data caching, avoid frequent or unnecessary cache invalidations. This might require splitting some collections into two separate collections: one that contains data likely to change frequently, and another whose data is not likely to be modified often, so its associated cache is less likely to be invalidated.

Cache invalidation and eventual consistency

Since cache invalidation might take a few seconds to complete, it increases the chance that out-of-date data could be returned to site visitors. This can make the effects of eventual consistency more noticeable.

To ensure that query results contain the most up-to-date data, you can override eventual consistency. When running the data query using find(), count(), or distinct(), set the options.consistentRead parameter to true. For example:

Data caching and site monitoring

Wix's site monitoring dashboard allows site collaborators to view and analyze site performance. At present, user requests that are served cached results are monitored but not displayed on the dashboard.

See also

• Wix data and eventual consistency
• Working with Wix app collections and code
• Working with the monitoring dashboard
• About page caching