Transport Presence signal Backpressure burden Best fit
Server-Sent Events Server owns the stream lifecycle Moderate Browser clients receiving updates
WebSocket Connection is bidirectional High Clients that also send frequent events
WebRTC data channel Peer connection exposes connection state Highest Direct peer-to-peer paths already required
Recommendation: accept driver coordinates through an authenticated HTTP endpoint, coalesce updates per work order, and publish the newest point over a server-owned stream. Treat presence as a leased state with an expiry, never as a synonym for an open socket. This keeps a property-management app honest when a maintenance driver enters a parking garage, changes networks, or closes the app. It also keeps the hot path small enough for a solo SaaS operator to ship and operate.
Short answer: throttle by replacing pending coordinates, not by delaying every coordinate.…