Issue 186: architecture: Implement Redis Pub/Sub for scaling WebSocket nodes

[AlAfiz]

Description

We hooked up our WebSocket server to broadcast live trades. However, if TradeFlow goes viral tomorrow and we have to spin up 5 different backend servers to handle the load, a user connected to Server A won't see a trade processed by Server B.
We need to implement Redis Pub/Sub (Publish/Subscribe).
When any backend node processes a trade, it publishes it to a Redis channel. All other nodes subscribe to that channel and forward the message to their connected WebSocket clients.
This is the industry standard for scaling real-time Web3 infrastructure.

Requirements

• Instantiate a redisPublisher and redisSubscriber client in the backend configuration.
• Have the redisSubscriber listen to a channel named live_trades.
• Update the Event Indexer daemon: when a trade is saved to the DB, use redisPublisher.publish('live_trades', JSON.stringify(trade)).
• When the subscriber receives a message, broadcast it to all local WebSocket connections.

[eleven-smg]

@nedzoey-svg has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’d like to work on this issue
I have experience with Node.js backends, WebSocket architecture, and event driven systems, including using Redis for Pub/Sub. I understand how to handle cross node message distribution, avoid inconsistencies, and keep latency low. I can implement a clean publisher/subscriber setup and ensure seamless broadcasting of trades across all connected clients.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nedzoey-svg to this issue.