Event Streaming (SSE)
Server-Sent Events and HTTP-friendly event streams: one-way delivery over standard ports, friendly to browsers and reverse proxies. Use this family when you need a sequential feed without upgrading to WebSockets, or when MQTT topic semantics are unnecessary. Live broadcasts and editorial streaming belong to dedicated portals; here we document technical event delivery for integrations.
How this differs from other Hub paths
MQTT for pub/sub and brokered topics; WebSockets for bidirectional sessions; REST for request/response. SSE fits pull-friendly, ordered sequences over HTTP: choose per integration shape, not marketing labels.
When SSE helps
Dashboards, notifications, and log tailing where the client opens one long-lived GET and reads events in order.
When to prefer MQTT or WS
Many publishers and subscribers on named topics: MQTT. Interactive or binary duplex workloads: WebSockets.
Integrate and discover
Continue integration work on Hub, or browse commercial discovery and catalogs on Coderic Network.