Caching is a technique that stores a copy of a given resource and serves it back when requested. When a web cache has a requested resource in its store, it intercepts the request and returns its copy instead of re-downloading from the originating server. This achieves several goals: it eases the load of the server that doesn’t need to serve all clients itself, and it improves performance by being closer to the client, i.e., it takes less time to transmit the resource back. For a website, it is a major component in achieving high performance. On the other side, it has to be configured properly as not all resources stay identical forever: it is important to cache a resource only until it changes, not longer.
Blackthorn uses several caching mechanisms to deliver the best performance we can at this time. As we grow, we will identify better scenarios to serve a larger customer basis.
When creating an event, the cache will be refreshed instantly. This means if an event is published or not, it will reflect accordingly on the front end.
When updating an event, updates to the following objects will trigger a refresh. Please keep in mind updating certain fields will not trigger a refresh. If a refresh is not triggered, please use the
Update button on the
BT Event Publish component on the Event page.
Updating the following objects will trigger a refresh:
- Session Attendee
- Event Content
- Custom Tabs
- Event FAQs
- Event Keywords
- Big List Groups
- Data Dictionary
Updated 2 months ago