Improved Cache Management
"There are only two hard things in Computer Science: cache invalidation and naming things." — Phil Karlton
Perhaps the most common issue our customers have run into when working with Divshot is basically a stale cache issue: "I just deployed a new version of my app, but it's not showing up." When this happens, we manually purge the cache and investigate the root cause. Usually it's a strange happenstance error (that is unlikely to repeat), sometimes it's a bug that we can address directly. But in either case, waiting for our support to resolve the issue is costing you, our intrepid users, time. We're not cool with that.
Today we're rolling out a set of improvements to address this head on. The most important is that we are exposing the ability to manually purge your application's cache. It's not something you should need to do regularly, but it's good to have if you need it. From the CLI, just run:
divshot purge [env]
production. If you want to purge everything for your app all at once, just run
divshot purge by itself.
You can also manually purge your application's cache from the app settings menu in the dashboard.
In addition to manual cache purging, we've taken steps to make sure even the unexpected errors happen less often. We're now automatically expiring caches on a regular basis to make sure if something has become stale, it doesn't stay that way for long. We've also made our cache invalidation more aggressive.
Our platform has always been engineered for reliability: we'd rather serve stale data than no data. These improvements allow us to make sure you have ultimate control over your site while keeping everything running fast and smooth. Happy hacking.