Server-Sent Events (SSE)
Definition
Server-Sent Events continuously transmit new events from the server to the browser.
A web standard where a server sends continuous text events to a browser over a long-open HTTP connection.
Simply explained
The browser keeps a connection open and receives new messages without having to repeatedly ask again.
Why it matters in practice
The term contributes to secure, maintainable, and high-performance web applications as well as resilient technical decisions.
Example from business
A web interface continuously shows status and text updates of a background process.
Limits and pitfalls
- Equating SSE with WebSocket, not handling reconnection and event IDs, or sending binary data directly.
Origin & history
SSE was standardized in HTML5 and is common for one-way server-to-client streaming.
Use in mid-sized companies
- Possible example: A web interface continuously shows status and text updates of a background process.
Frequently asked questions
What does Server-Sent Events (SSE) mean?
A web standard where a server sends continuous text events to a browser over a long-open HTTP connection. What mistakes should be avoided? Equating SSE with WebSocket, not handling reconnection and event IDs, or sending binary data directly.
Sources
Source checked on 10.10.2026. Editorial application examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: