Menu

Node.js Queue-to-Publish Design — Durable Alerts for Offline Fintech Users
📰

Node.js Queue-to-Publish Design — Durable Alerts for Offline Fintech Users

DEV Community: node·GageSterling2648·10 days ago
#Qx35snT4
#devtonodejs#devto#dev#inbox#presence
Reading 0:00
15s threshold

Presence should decide whether a fintech notification gets an immediate push, never whether the notification exists. Short answer: in a Node.js queue-and-publish service, commit each alert to a server-side inbox, enqueue its side effects, make one best-effort publish attempt for connected clients, and let offline users get notified by reading that inbox after reconnect. Keep read state on the server so a phone and a browser converge on the same answer.

This gives you two viable system shapes. A durable-inbox design is the default for transaction alerts. A session-led design can be useful when the event belongs to a live advisory room and its artefacts must outlive that room. Neither design turns a realtime publish into durable storage.

Infrai fits the second shape when a team wants realtime/RTC and private storage behind one REST API and one key.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.