A option for real-time communication could be peer.js, it works with WebRTC peer-to-peer data without sending chat data through a server. In other words, you don't store the chat data, but only provide the connection between users.
But if you want to store all chat data than I personally prefer mysql. I do not know for sure if, for example, chat data better be stored in a nosql database.
Thanks so much, I will check peer.js.
I never knew WebRTC never goes through the server, that makes it unlike Websocket.
But for chat data I'm using PostgreSQL. I love to leverage upon "relational" in RDBMS. I prefer it to NoSQL/Document DB, too
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A option for real-time communication could be peer.js, it works with WebRTC peer-to-peer data without sending chat data through a server. In other words, you don't store the chat data, but only provide the connection between users.
But if you want to store all chat data than I personally prefer mysql. I do not know for sure if, for example, chat data better be stored in a nosql database.
Success!
Thanks so much, I will check peer.js.
I never knew WebRTC never goes through the server, that makes it unlike Websocket.
But for chat data I'm using PostgreSQL. I love to leverage upon "relational" in RDBMS. I prefer it to NoSQL/Document DB, too