Update Freeway to send the egress event to a CloudFlare queue instead of invoking the Upload API directly

[fforbeck]

Context

The Freeway Worker currently processes approximately 2.5 billion requests per month. For the second phase of the Egress Billing System rollout, we need to ensure the egress tracking feature scales to handle all incoming requests effectively.

The proposed solution involves updating the Freeway Worker to enqueue events in a Cloudflare queue. Consumers will then process these events asynchronously and handle invocations to the upload-api.

graph LR
    A[Freeway Worker] -->|Sends Egress Events| B[Cloudflare Queue]
    B -->|Dispatch Events| C[Event Consumers]
    C -->|Perform Invocations| D[Upload API]

Loading

1. The Freeway Worker generates egress events and enqueues them in a Cloudflare queue.
2. Event consumers process the queued events asynchronously.
3. The consumers invoke the upload-api to log egress data.

Docs

• https://developers.cloudflare.com/queues/reference/how-queues-works
• https://developers.cloudflare.com/queues/get-started
• https://developers.cloudflare.com/queues/configuration/javascript-apis