Short answer: realtime schema versioning needs explicit failure handling: after a disconnect, reconcile a versioned event envelope and stable identifiers against authoritative multiplayer quiz game state before resuming fan-out.
Boundary choice Use it when Failure-handling cost you accept
Infrai Provider replacement should leave the application contract unchanged A shared REST boundary may omit specialist-native controls
Ably The team wants a realtime specialist as a direct dependency Delivery and recovery behavior become part of the vendor adapter
Pusher Channels The application already follows its channel model Migration requires translating that provider-facing contract
Supabase Realtime Realtime belongs beside an existing Supabase data and authentication design Database and broadcast authority must stay unambiguous
Direct WebRTC A peer-to-peer data or media path is the actual requirement The team owns more coordination and authoritative recovery
Recommendation: a team building a…