Vercel Blob now supports consistent reads on private storage. Pass
A blob written to a fresh pathname has no existing cached entry, so reads reflect the latest write immediately. When you overwrite a blob at an existing pathname, readers might see the cached version for up to 60 seconds.
When a read must reflect the latest write, like an agent's memory file, a session transcript, or a scheduled JSON report, pass
You can also bypass the cache without the SDK. Under the hood,
Install the latest
Learn more in the consistent reads documentation.
Read more
Continue reading...
useCache: false to get() or presignUrl() for a read that reflects the latest write.A blob written to a fresh pathname has no existing cached entry, so reads reflect the latest write immediately. When you overwrite a blob at an existing pathname, readers might see the cached version for up to 60 seconds.
When a read must reflect the latest write, like an agent's memory file, a session transcript, or a scheduled JSON report, pass
useCache: false. These reads bypass the CDN, take longer than cached reads, and incur Fast Origin Transfer.You can also bypass the cache without the SDK. Under the hood,
useCache: false adds a cache=0 query parameter to the request. You can set it yourself on a private blob URL:Install the latest
@vercel/blob SDK for consistent reads:Learn more in the consistent reads documentation.
Read more
Continue reading...