| id | SKL-server-SERVERSENTEVENTS |
| name | Server Sent Events |
| description | Server-Sent Events (SSE) enable servers to push updates to clients over HTTP. This guide covers implementation, use cases, and best practices for building real-time features using unidirectional event |
| version | 1.0.0 |
| status | active |
| owner | @cerebra-team |
| last_updated | 2026-02-22 |
| category | Backend |
| tags | ["api","backend","server","database"] |
| stack | ["Python","Node.js","REST API","GraphQL"] |
| difficulty | Intermediate |
Server Sent Events
Skill Profile
(Select at least one profile to enable specific modules)
Overview
Server-Sent Events (SSE) enable servers to push updates to clients over HTTP. This guide covers implementation, use cases, and best practices for building real-time features using unidirectional event streams.
Why This Matters
- Simplicity: Built on HTTP, no WebSocket complexity
- Reliability: Automatic reconnection built-in
- Compatibility: Works through firewalls and proxies
- Efficiency: Less overhead than polling
Core Concepts & Rules
1. Core Principles
- Follow established patterns and conventions
- Maintain consistency across codebase
- Document decisions and trade-offs
2. Implementation Guidelines
- Start with the simplest viable solution
- Iterate based on feedback and requirements
- Test thoroughly before deployment
Inputs / Outputs / Contracts
- Inputs:
- Event endpoint URL
- Authentication token (optional)
- Event types and data formats
- Update interval or trigger conditions
- Entry Conditions:
- HTTP server configured
- Event sources connected
- Client EventSource API available
- Authentication system in place
- Outputs:
- Real-time event stream
- Connection status updates
- Event data to clients
- Error notifications
- Artifacts Required (Deliverables):
- SSE server implementation
- SSE client hook
- Event streaming service
- Connection management
