Building Waiting Room on Workers and Durable Objects
It is definitely a neat feature.  And just scratches the surface of what workers and durable objects can do.<p>To what extent though, would such a feature be necessary if the application had been designed properly from the ground up to scale?  That could still mean using workers and durable objects.<p>Having the logic handled on workers themselves rather than some inherently unscalable legacy stack may be a better solution.  Bottom line, if your application needs a waiting room, you have more fundamental problems.<p>This is a poor use of the engineering talents at Cloudflare.  Probably something pushed for by the sales team seeking to satisfy potential clients using legacy stacks.  Going forward, hope this does not skew the objectives of the engineering teams.<p>What would a better use of engineering talents at Cloudflare be while addressing the same root problem of overload?  Exploring the ways in which the needless complexity of kubernetes can be supplanted - most notably with shared multiple tunnel instances.