30 discussions in the community
we're designing a notification system for a social platform with around 10 million users, and we're debating between fan-out on write versus fan-out o...
we've started seeing some abuse patterns on our websocket endpoints, with clients opening hundreds of connections or sending thousands of messages per...
building a notification system for a social platform with millions of users always brings up the fan-out on write vs. fan-out on read dilemma. we have...
we've been using server-sent events (sse) in production for about two years now for all our real-time notifications, and it's been mostly stable. howe...
Our backend team is heavily invested in an event-driven architecture, which works great for scalability and decoupling. However, our frontend team is ...
we're trying to build out a robust presence system, something like what slack has, where you can see who's online and actively using the app. it sound...
we're looking to build a slack-like presence system to show which users are currently online. the main challenges are scaling to 500k+ concurrent user...
building a chat system, and handling message delivery guarantees is proving to be complex. we need read receipts, typing indicators, and offline messa...
we're seeing incredible growth in our real-time features, and we're now approaching 500k concurrent websocket connections to our existing gateway. it'...
we've started seeing some abuse on our websocket connections, with individual users (or bots) opening hundreds of connections or sending thousands of ...
we're dealing with a rapidly growing number of websocket connections, currently around 500k concurrent users, and our single websocket gateway is beco...
we're building a slack-like presence system, needing to know who's online and propagate those changes quickly to hundreds of thousands of users. the c...
our backend team has fully embraced event-driven architecture, and it's working really well for decoupling services and scaling. the frontend, however...
when designing real-time features, the choice between websockets, sse, and long polling feels like a constant debate. at work, we're often dealing wit...
we have an analytics dashboard that currently polls an api every 5 seconds for updates. the data is relatively small, but the polling traffic adds up....
we've been using server-sent events (sse) in production for our internal notification system for over two years now, serving tens of thousands of conc...
we're looking at implementing real-time server-to-client notifications for around 100k concurrent users, and trying to decide between websockets, serv...
we're building a new chat system and struggling with message delivery guarantees. we need to handle read receipts, typing indicators, and offline mess...
we're exploring building a collaborative editing feature similar to google docs, and the core choice is between operational transformation (ot) and co...
We're currently dealing with scaling our WebSocket connections and it's becoming a significant bottleneck. We're approaching 500,000 concurrent connec...
