[somishere]

Biggest advantage I find is pre-scoped request-level control over everything. When someone loads your page, every single asset request hits your worker. It's both extremely simple and exceptionally powerful. Choose which responses to modify, authenticate, proxy, redirect, or let through. All in a single file with a few dozen LOC. No complex pre-app devops, middleware or routing policies required (i.e. oh sorry that route is proxied by a lambda, or you should check the cloudflare dash there's a worker sitting in front of that).

Yes, there are a bunch of limitations - but in practice I quite appreciate the boundaries and the reasoning. There's also the portability question, but we're talking about PaaS. As someone who was using Firebase for many years, and static AWS + lambda prior to that I find this evolution entirely refreshing.

I've pushed 5 personal projects on pages since Jan and working on more. Most recently https://thesom.au/gh/cvms

[tarasglek]

Author here, went through your github. Cloudflare should post your code as reference architecture. Answered so many questions re proper app structure on CF. Really appreciate the amount of effort your examples will save me in future.

[somishere]

Thanks for the kind words - though not certain too many would share your enthusiasm! Good luck with the tinkering.

[superdug]

I'm curious about cams, but I'm being greeted with "Your passphrase has expired" when I try to get it to "let me in"

[somishere]

Thanks for the heads up. There's nothing mind blowing on the demo page, but password has been unexpired if you still want to take a look.

[superdug]

It looks like something interesting, I sent an email as I got stuck after the read me and haven't had a lot of time to poke around in the code.

[somishere]

Replied. Cheers!