Hi everyone 👋

We've had good news on the new business front this week, with a new engagement confirmed today.

The network team have been working on a series of refactors for the queue process, adding some additional clarity and a rebalancing in the repetition of jobs, increasing overall performance.

Cache pre-warming methods have been added to Content Distribution. This is a system that Gateway uses to re-issue requests for items that are heavily accessed during their time in the cache, meaning that they are in effect persisted in the cache in a way that removes the first load delay for new objects entering in to the service layer.

This is seriously cool tech, and a really powerful and unique feature.

Arthur will be writing more about this in the coming week or so.

The Content Distribution service has been extended to include a header to identify whether a result was created by a user triggered action or by the pre-warming system.

The team also added functionality that enables the pre-warmers ability to persist an expired cached object until it has been successfully re-warmed, removing the potential for service outage and ensuring consistent object delivery.

A new command was introduced to edge-cli, check, which performs a series of connectivity and system checks to make sure the Device is fully capable of delivering as a Host.

You can read more about this here: https://edge.network/en/knowledge/network/edge-cli-connectivity-check/

And that's it for now!

Enjoy your weekends.