RFC about websockets for the messaging system

[JoseNoriegaa]

Hi, this is the RFC about the websockets implementation for the messaging system.

Members:
@JoseNoriegaa
@taberoajorge

[Basultobd]

Some comments

1. In the diagram, when we ask REST API to create a new Chat Room and this one return with a response, will we grab the id and create a new socket connection?
2. How is the performance handling multiple socket connections?
3. At socket implementation code level, how we are going to handle a conenction between two users? In which moment the new connection will be created? The chat component render?

[JoseNoriegaa]

1- Since we changed the design a little bit, the moment when a new chat room is created is a little bit confusing, we didn't find a solution yet.
2- We are goin to use Redis with the pub-sub pattern to improve the performance.
3- The idea is that once the user is authenticated, the application should open a ws connection because the "messages" section is always visible in the user section inside of the header component. If we don't want to track chat conversations everywhere, we can initialize the ws connection once the user enters to the chat page.

[JoseNoriegaa]

@Basultobd We updated the diagram that answers the first question.