Today, resource binaries get persisted in Akamai NetStorage. The per tenant Edge Configuration maps specific folders of NetStorage to corresponding URL patterns such that those resource can be served through the edge directly from NetStorage.

This was done driven by performance and scalability goals.

NetStorage is pretty expensive - it would be cheaper for us to store the binaries in IBM Cloud Object Store. Directly mapping COS from the edge config is probably difficult to do - but the alternative would be to serve everything through DRS. This would put more load on our system - but at the same time make our implementation model for advanced resource delivery features like "access controls", "custom HTTP headers" and "Custom re-routings - e.g. SPA kicker routings" easier - since we could control all of that from within DRS instead to updating the static Akamai edge config for this.

more background can be found here: https://github.ibm.com/DX/squad-publishing/blob/master/Resource%20persistence%20and%20delivery.pptx

Idea is to do a PoC - and measure runtime behavior to validate this approach. If it turns out that this is a valid option, the earlier we move the better ...