@pfefferleMatthias Pfefferle on "How is this diff from WS?" for streaming, Server Sent Events is unidirectional, you get what you originally requested.

WIth websockets, you can do bidirectional "oh, I want these notifications on this resource", "oh, I'm not interested in that anymore, give me notifications on this other resource" (essentially adapting)

SSE vs Websockets also has automatic vs manual cursor resumption — SSE will automatically tell the server "this is the last ID I knew, give me events since then", where as with websockets you need to make that yourself via like a `cursor` parameter in the URL.