Vercel Blob Adds Support for Consistent Reads in Private Storage

Vercel Blob has started supporting Consistent Reads in private storage. Previously, when overwriting a Blob at an existing path, read requests could return a cached version for up to 60 seconds.

Now, passing the useCache: false option to the get() or presignUrl() function allows you to bypass the CDN and get reads that immediately reflect the latest write state. This is useful for tasks where reflecting the latest data is essential, such as agent memory files, session transcripts, and scheduled JSON reports.

However, cache-bypassing reads have the following characteristics:

• CDN Bypass: Fetches data directly from the origin instead of using cached data.
• Performance and Cost: Takes longer than cached reads, and may incur Fast Origin Transfer costs.
• Direct Implementation: Even without using the SDK, you can bypass the cache by adding the cache=0 query parameter to the end of the URL.

To use this feature, you need to update the @vercel/blob SDK to version 2.6.1 or higher.