Three-channel notifications without drama or “oops, it didn’t get there”
At WikiMind, we grouped notifications into 3 channels so important things don’t get lost even when the user is offline. REST, WebSocket, and Email work together without overengineering.
In WikiMind, we put notifications into 3 channels so important things don’t get lost, even if the user’s Wi‑Fi decides to take a vacation at that moment.
How we set it up:
- REST API — the bell in the UI, reads notifications from the DB
- WebSocket — real-time pushes, exactly how people like it in 2025: fast, native, no refresh
- Email — async via
Taskiq, without blocking the main thread
If the user is offline, the WebSocket message is lost — but that’s not critical: the notification still stays in the DB and is later picked up through REST. A kind of fallback, but it works, without overengineering.
What we send: @mention, adding someone to a group, changing access rights.
And for access-grant emails, we include a direct link to the document — one click, and the person is already inside, without the “where do I open this?” quest.
Sometimes reliability isn’t rocket science, just decent multi-channel delivery 🙂