From 91020231f8edd9ae5b1b16dff40a3642dc4f0fe0 Mon Sep 17 00:00:00 2001 From: Atridad Lahiji Date: Tue, 23 Apr 2024 22:13:30 -0600 Subject: [PATCH] Updated URL --- content/scalable-realtime-apps-with-fly-and-remix.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/scalable-realtime-apps-with-fly-and-remix.md b/content/scalable-realtime-apps-with-fly-and-remix.md index 0ed855e..6782850 100644 --- a/content/scalable-realtime-apps-with-fly-and-remix.md +++ b/content/scalable-realtime-apps-with-fly-and-remix.md @@ -17,7 +17,7 @@ Real-time applications require a pub/sub or publish and subscribe model. A clien For this stack, I chose Remix for its close adherence to web standards and easy support for server-sent events. These web socket connections work one way: from server to client. Next, we must synchronize all Server Sent events across different requests to a single node. For this, Node.js has its own Event Emitter API, which we can use. Now, we can use something like Redis and its Pub/Sub commands for multi-node setups to broadcast across nodes. This is what it would look like: -![Diagram](https://link.storjshare.io/s/jwmhimh32pura4pyr5h5luou6qla/atridad%2Farticles/scalability.png?wrap=0) +![Diagram](https://srv.atri.dad/articles%2Fscalability.png) # How does it work?