Introducing Cold Storage for Constructs

As your project grows and you accumulate more content, you may find that not all of it requires active management. Some content will likely be historical, archival, or simply not relevant to your current audience.

You could remove this content to cut down costs, but what if it's indexed by search engines, or referenced in other content? You probably want to keep it around, even if just to avoid 404s, but it would be a shame to pay for content management for content you won't be managing.

It may even be a requirement to retain this content for a period of time, for compliance reasons, or to meet contractual obligations.

This is where Cold Storage comes in.

Cold Storage

Cold Storage is a simple concept. When you no longer need to manage a construct (i.e. a single content item), you move it to Cold Storage. This single click operation takes your construct out of the regular content management workflow, and into a storage state where it is retained, but can not be managed, or queried.

Once in Cold Storage, a construct is no longer accessible over the Delivery API, but instead is served from the Cold Storage API. The Cold Storage API mirrors the Delivery API, but only includes constructs in Cold Storage, and does not support filtering, sorting, or pagination. It simply returns the construct as a static JSON resource.

Of course, if you need to manage it again, you can simply move it back out of Cold Storage, and it will be restored to its original state.

Start Kit Integration

All of our starter kits have been updated to support Cold Storage. When encountering a construct in Cold Storage, the starter kit will automatically fetch the static JSON resource from the Cold Storage API, and make it available to your application locally.

This means that your resource will continue to be accessible directly, but not in queries. So, for example, if you have a blog post in Cold Storage, it will be accessible at /blog/my-cold-post, but it will not be returned in a query for the latest posts. This is exactly what you want for content that is no longer relevant, but still needs to be accessible.

Costs and Limit

Cold Storage itself is free, but it will impact your API usage. Typically, this will be negligible, as our starter kits will cache Cold Storage constructs indefinitely.

To avoid abuse, you are limited to 25% of your total constructs being in Cold Storage at any one time. The mechanism is for active projects, not whole project archival. If you need more Cold Storage, please contact us and we can, on a case-by-case basis, grant a higher limit.