Server Sent Events are still not production ready after a decade. A lesson for me, a warning for you! - DEV Community
dev.to · 4,056 words · saved by 1 readers
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
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
- Everything I know about good system designseangoedecke.com
- The simplest way to add server sent events to Django 🏺 - Tom Dekanphotondesigner.com
- WebSockets, caution required!samsaffron.com
- RSC From Scratch. Part 1: Server Components · reactwg server-components · Discussion #5github.com
- Notes on Distributed Systems for Young Bloods – Something Similarsomethingsimilar.com
- Making Sense of React Server Components • Josh W. Comeaujoshwcomeau.com
- Thoughts on slowing the fuck downmariozechner.at
- We migrated 50,000 lines of code to React Server Componentsmux.com
- The service worker lifecycle | Articles | web.devweb.dev
- Queues Don't Fix Overloadferd.ca