Hello Michael. I have watched this video no less than ten times. Cudos to you for presenting such a compelling and exciting strategy for performance. I am having difficulty implementing this approach into my current project(s) particularly implementing the bucket proxy and storage.

I am getting the following error (I added 'err' to Not Found in app.ts in rs.on("error"):
Not Found: ApiError: No such object: xxxxx.appspot.com/some-folder/some-file.html

Questions:

1. Do I have to load storage with static files of each possible request, i.e. one per document in Firestore?
2. Or should I build in a test to see if the file exists in storage, and if not, render the page and deliver a copy to storage afterwards, and if so, how is this accomplished?
3. Is there more information besides the video, e.g. blog article or tutorial?

Thank you so much @mbleigh !!

I really like the idea you describe about Evented Rendering here: https://youtu.be/7_2CJs_VZk4?t=1720

Maybe I'm missing something, but wouldn't it be possible to end up with stale contend for a whole year (worst case) in your example? I see the following scenario:

1. A region gets updated.
2. updateRegionPage() is called. This prerenders the page.
3. writeAndPurge() is called. This writes the prerendered page to Cloud Storage and purges the page on Firebase Hosting.
4. The next time the page is requested, Firebase Hosting serves it from Cloud Storage via Cloud Functions (with a CDN cache s-maxage of one year).

Imagine that while the Cloud Function in step 4 is running, the region gets updated a second time which starts the process again. The following could be possible:

(Process 1): Is not finished with step 4. It already has the stale page from Cloud Storage but hasn't served it yet.
(Process 2): Goes through step 3. It prerenders and purges the page.
(Process 1): Finishes with step 4. This means that Firebase Hosting serves the stale page and caches it for a year.

I don't know how likely this is but it would be quite bad if it happens since it is really hard to find the bug and the client has no possibility to get the correctly rendered page for potentially a whole year.

I hope that I'm wrong. Or is there anything you could do about that?