DiceDB / dice

DiceDB is a redis-compliant, reactive, scalable, highly-available, unified cache optimized for modern hardware.
https://dicedb.io/
Other
6.88k stars 1.09k forks source link

POC for WebSocket Integration with DiceDB #556

Open pratikpandey21 opened 2 months ago

pratikpandey21 commented 2 months ago

Description:

Create a Proof of Concept (POC) demonstrating the use of WebSocket support in DiceDB by developing a new example application called leaderboard-ws. This example will showcase how clients can directly connect to DiceDB via WebSocket to receive real-time updates, similar to the existing leaderboard-go example.

POC Requirements:

Leaderboard Example Using WebSocket:

  1. Develop a new example called leaderboard-ws, where the client connects directly to the DiceDB server via WebSocket.
  2. Demonstrate the use of WebSocket for real-time communication, where the client receives instant updates on changes to the leaderboard data.
  3. Concrete Example with Documentation:
pratikpandey21 commented 2 months ago

Depends on #555

Saumay commented 2 months ago

@pratikpandey21 Would like to pick this up.

lucifercr07 commented 2 months ago

@Saumay thanks for contributing, assigned.

Soham041201 commented 2 months ago

@Saumay Are you still working on this?

Saumay commented 2 months ago

Yes, I'll be working on this issue.

@Soham041201 , this is dependent on #555. It can't be started till #555 is merged.

lucifercr07 commented 2 months ago

@Saumay PR for websocket integration has been merged now.

Saumay commented 2 months ago

@lucifercr07 Awesome. Let me get started with this.

Saumay commented 1 month ago

@pratikpandey21 Correct me if I am wrong but this requires DiceDB Websocket server to support QWATCH queries(for receiving real-time updates), right?

psrvere commented 1 month ago

@Saumay - QWATCH support for websocket PR is under review right now. #1090

arpitbbhayani commented 1 month ago

Hello @Saumay,

There has been no activity on this issue for the past 5 days. It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.

We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.

Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.

Thanks again.

Saumay commented 2 weeks ago

Hey @arpitbbhayani , this was dependent on a few issues and hence didn't look into this actively. Seems those issues are merged now. Let me quickly wrap this up.