Thanks very much Isabella!

Thanks very much Hamid 🫡

Hi! If your channel contains changes in state, for example with changing betting odds like spurs to win is now 5/1, then the original (already existing) state does come from a database, as you mentioned. Ably’s LiveSync is designed to deal with exactly this problem by merging together an existing database state with changing states communicated by Ably channels.

Thanks so much !

Thanks for commenting!

This is often not possible with phones or tablets due to constraints from Apple and Android with apps not allowing background WebSocket connections. It is not even possible to send REST https requests to apps running in the background. The only way around is to send a push notification. If the app is running in the foreground indefinitely, the socket connection can stay open.

Hey there! Redis is used in this situation more as a cache, optimised brokering the messages with ultra low latency. The classic design to persist messages longterm is to have an additional relational DB as a layer after Redis (to the right in the diagram)

Yes, this would be a recommended design pattern, and has increased security benefits over navigating rooms and servers using naming patterns. Thanks for your question!

@@AblyRealtime I appreciate your reply!

we will next time 🥰

You have to set-up a way to provision and shed Redis instances to match scaling demands. Some use-cases will demand a Kubernetes type service to manage the instances, and others a more homegrown solution.

Alex is just a VS code white-mode kinda guy 😎

😁

Great to hear from you, and thanks for commenting ❤️

Haha, no way, amazing to see you here! Great work on react-use-websocket!

Alex from the video here 👋🏻 That is a good question. WebSockets are a realtime communication protocol that provides a full-duplex communication channel between client and server over a long-lived connection, meanwhile Redis is an in-memory data structure store. Sometimes confusion can arise because Redis does support pub/sub, but that mechanism is primarily designed to handle communication between your app/services and Redis. It's not suitable for realtime interaction between your server and clients (end-users). For example, you'd be hard-pressed to connect to Redis from a browser in a a sensible way but that's exactly what Websockets are designed for.

@@AblyRealtime Thank you for the reply. Websocket for the realtime experience.

🫣

Hi Eduardo. It is possible to send messages with total data size of up to 64kb within an Ably message. Unfortunately, we do not by default support sending files larger than this over the WebSocket connection, but a common way to solve this problem is to send an access url in the Ably message which links to an external database. Would this work for you?

Thanks for your feedback! If you're interested, this is certainly the kind of content we'll consider delving deeper into in the future.

You’re spot-on, except Redis is well-suited for clustering compared to your own WebSocket server.

Alex from the video here 👋🏻 Unfortunately, no. From what I learned, you can’t really pass data from client to server components, you have to fetch all of it upfront and only use the client component to control what gets displayed.

Hey, what do you need help with?

Thank you for your kind words! We're glad to hear you found our explanation helpful

Fucking spam

Thanks! Glad to hear you liked it!

Thanks for the suggestion! We'll keep this in mind for future videos.

Thanks for letting us know, a great suggestion!

Sounds like a perfect application for Ably! Glad to hear you're having a good experience - Alex

React useWebSocket forces a render when lastJsonMessage is updated. In other words, the component renders every time a new WebSocket message is received - Alex