6 reasons to think twice before using WebSocket
summary
Talk surveys six reasons to think twice before using WebSocket for web applications, focusing on practical pitfalls and trade-offs. It discusses common problems developers encounter when building WebSocket services (with examples relevant to FastAPI) and provides a 'map of pitfalls' to help newer developers avoid those mistakes.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:28What is WebSocket
- 3:13State consistency issues
- 8:15Push model costs
- 10:20Event ordering problems
- 12:24Scaling WebSocket
- 15:56Authentication issues
- 19:53Unauthorized access risks
- 21:41Network instability
- 24:13Standard extensions
- 25:37Documentation problems
- 28:09Six WebSocket rules
- 40:07Q&A
related talks
41mWebsockets as the glue to interactivity
30m⛳️ Does Your Web API Pass the 60-Point Safety Check?
01h 23mWhy Slow?
01h 02mFive things every developer should know about building mission-critical systems
40mThe Road to 2 Million Websocket Connections in Phoenix
21mDecisions & considerations in building your WebRTC app
57mWhy and how to transform a REST API into a Data Streaming API
32mA Modern Web Landscape — Matt Biilmann, Frances Berriman, and Wilson Miner