> it's much, much harder to build a streaming functionality compared to plain request/response if you've got some notion of a "session" This touches something

> it's much, much harder to build a streaming functionality compared to plain request/response if you've got some notion of a "session" This touches something that I think is starting to become understood- the concept of a "session backend" to address this kind of use case. See the complexity of disaggregation a live session backend on AWS versus CloudFlare: https://digest.browsertech.com/archive/browsertech-digest-cloudflares-durable/ https://digest.browsertech.com/archive/browsertech-digest-cl... I wrote about session backends as distinct from durable execution: https://crabmusket.net/2024/durable-execution-versus-session-backends/ https://crabmusket.net/2024/durable-execution-versus-session...