docs: add conceptual documentation for presence and heartbeat services - #489
Open
Samuel-21-eng wants to merge 1 commit into
Open
docs: add conceptual documentation for presence and heartbeat services#489Samuel-21-eng wants to merge 1 commit into
Samuel-21-eng wants to merge 1 commit into
Conversation
|
@Samuel-21-eng Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Owner
|
Hello @Samuel-21-eng |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The new documentation apps/backend/docs/concepts-presence-heartbeat.md provides a comprehensive overview of the
backend's presence and heartbeat mechanisms:
device sessions, and socket mappings, including their purpose and TTL logic.
connection liveness and the 30-second throttle for database updates to balance precision with performance.
user's overall "online" status and the conditions for broadcasting state transitions (user_offline).
remain consistent after service restarts.
This document serves as the canonical reference for understanding how client connections are maintained, timed out,
and synchronized across the distributed backend architecture.
closes #447