Investigate options/impact of edge routing vs subdomain hosting [0.5 days]

[Harjot1Singh]

Motivation

Since we'd like to point some APIs to buckets, and others to something that dynamically runs, there is a question around how we'd surface this as a consistent API URL. We'd like developers to always be able to access the Content API at the same place, in the same way, and allow us to update this over time.

We do not want to introduce unnecessary latency and kill the speed of our API for "cosmetic" reasons.

There are two broad options:

• Edge workers to handle routing - this will mean we'll incur run costs for hits to this, but it won't be a problem if we're planning to route through edge workers anyway
• DNS to update hosts directly: content.api.shabados.com/content.shabados.com

Goal

A PoC of an edge router communicating with another worker to investigate the performance impact of the additional call.

[swissarmykirpan]

We also need to consider how we are going to control the access to the blobs as well as managing things like throttling