[Backend] — Live Odds WebSocket Channel per Market

[Olowodarey]

Labels: backend, enhancement, websocket, markets

Problem

Clients must poll for odds updates because there is no push channel delivering per-market odds changes in real time.

Requirements

1. Add a subscribe/unsubscribe flow for per-market odds rooms in the gateway.
2. Broadcast odds updates to a market's room when they change.
3. Throttle broadcasts to a configurable max frequency.
4. Clean up empty rooms and handle disconnects.

Acceptance Criteria

• Subscribers to a market receive odds updates without polling.
• Broadcast frequency respects the configured throttle.
• Rooms are cleaned up on last unsubscribe/disconnect.
• Tests cover subscribe, broadcast, and cleanup.

Files

backend/src/websocket/events.gateway.ts, backend/src/websocket/broadcaster.service.ts, backend/src/websocket/websocket.module.ts

[JesseJohn7]

@JesseJohn7 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer can I please work on this issue

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

[glorious21-coder]

@glorious21-coder has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I’d appreciate the opportunity to contribute to this issue. I’m detail-oriented and committed to delivering quality work.

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

[bright5455]

@bright5455 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello Maintainers,

I’d like to be assigned to this issue.

I have experience building real-time backend applications with NestJS, WebSockets, PostgreSQL, and Prisma. I understand that continuously polling for odds is inefficient and increases unnecessary server load. A dedicated WebSocket channel per market is a better solution because it delivers updates instantly while reducing network traffic.

My implementation plan

1. Review the existing WebSocket gateway and event flow to understand how clients currently receive updates.
2. Implement a subscribe/unsubscribe mechanism that allows clients to join or leave market-specific rooms using a market identifier.
3. Ensure clients only receive updates for the markets they have subscribed to, preventing unnecessary broadcasts.
4. Integrate the odds update service with the gateway so that whenever odds change, only subscribers of the affected market receive the update.
5. Add validation for market IDs and handle invalid subscriptions or disconnected clients gracefully.
6. Include logging for subscriptions, unsubscriptions, broadcasts, and connection lifecycle events to improve observability.
7. Write comprehensive unit and integration tests covering subscriptions, unsubscriptions, real-time broadcasts, reconnections, and edge cases.
8. Verify that the implementation is scalable, follows the existing project architecture, and satisfies all acceptance criteria before submitting the PR.

My goal is to deliver a clean, efficient, and maintainable implementation that improves real-time performance while keeping the WebSocket layer easy to extend in the future.

I’d appreciate the opportunity to work on this issue and contribute a well-tested, production-ready solution. Thank you for your consideration.

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

[Awointa]

@Awointa has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to work on this issue. I'll add per-market odds WebSocket channels in the gateway with subscribe/unsubscribe flow, broadcast odds updates to market rooms with configurable throttling, clean up empty rooms on last unsubscribe/disconnect. Tests will cover subscribe, broadcast, and cleanup paths. Branch: feature/live-odds-websocket.

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

[Mkalbani]

@Mkalbani has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainers, can I work on this. I've worked on a similar work. Thank you.

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

[drips-wave]

Congratulations, @Awointa! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Awointa: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊