pipeline-de-notificacoes-em-tempo-real

What problem does it solve? Delivering instant notifications for collaborative editing events—such as @mentions in comments, collaborator cursors, and completed async jobs—requires a scalable real-time architecture that works across multiple server instances, which is complex to design correctly. ## Core Features & Use Cases - WebSocket Rooms with Socket.io: Authenticate clients via JWT handshake and organize sockets into per-document and per-user rooms for targeted event delivery. - @Mention Notifications: Resolve @username references in comments, emit real-time notification events, and persist them in a notifications table for offline retrieval. - Redis Pub/Sub Fanout: Use the socket.io-redis adapter so notifications generated on one server reach users connected to other servers in a cluster. - SSE for Non-Urgent Events: Deliver lower-priority updates like export completion via Server-Sent Events with heartbeat keepalive. - Use Case: When Maria comments "@joao check this scene", the server resolves the mention, emits a notification to João's socket room, and João sees a badge on his notification bell in under 500ms. ## Quick Start Implement the real-time notification pipeline with Socket.io rooms, Redis adapter, and SSE endpoints following the step-by-step process in this skill.