Server Sent Events are still not production ready after a decade. A lesson for me, a warning for you! - DEV Community

TL;DR I've had an incident with SSE that's caused real client pain, I detail it...

TL;DR I've had an incident with SSE that's caused real client pain, I detail it below Server Sent Events are a long established and recommended method of pushing from the server to the client Many articles proclaim their benefits like automatic reconnection including catching up on missed messages, being easier and more reliable than sockets etc Buried down in the spec, in the fine print, is something that renders them completely unreliable in uncontrolled environments (apps and public websites that must be generally available) Don't expect your events to get delivered any time soon on some co

saved by

• Tazik Sh

related reading

• What Server-Sent Events is - and how and when to implement it | Ably Realtimeably.com
• Realtime data streaming using server-sent events(SSE) with react.js and node.js - DEV Communitydev.to
• How it works | Socket.IOsocket.io
• Making Sense of React Server Components • Josh W. Comeaujoshwcomeau.com
• WebSockets, caution required!samsaffron.com
• The simplest way to add server sent events to Django 🏺 - Tom Dekanphotondesigner.com
• Navigating the future of frontendfrontendmastery.com
• Mediumcodeburst.io
• The weirdly obscure art of Streamed HTML - DEV Communitydev.to
• The ultimate SO_LINGER page, or: why is my tcp not reliableblog.netherlabs.nl
• Markov's Salonmarkovs-salon.vercel.app
• Designing a Concurrent Application | Learn You Some Erlang for Great Good!learnyousomeerlang.com