With the new update (thank you Wappler team, truly brilliant work @George, @patrick and @Teodor) I was wondering what everyone’s thoughts are on live chat.
Without knowing this was coming, I started looking into and planned to use the Twilio chat, plus GetStream for handling notificatons (I might still) - and wondered for chat, considering the volume that can appear, would it be recommended or normal practise for chat to have it’s entire own DB, or a table in the existing DB would be considered fine?
UPDATE:
Did a bit of research on this, this morning - it does appear most tend to create a new DB specifically for this. Postgres seems to be a popular choice. Still keen to hear any opinions on this!
This is something I’ll probably look into myself for my own app, but it’s probably not a day 1 feature so I’m still a bit away and bit much help.
I’d think though that there really is no disadvantage to having its own db. It’s not like it would need to it would need to sit in its own instance/droplet etc
It would just be another database in your existing db…and now with global db connections would be quite easy to manage.
I’d think building a simple in house chat functionality wouldn’t be too hard…and something fun to figure out. Good luck with your decisions.
After the socket feature is completed (I think it will be added within this week. or after Christmas), a chat application and many things can be done with the namespace and room.
Thanks @Hyperbytes, but I'm talking about a in-house user-to-user chat, rather than customer support etc.. you are right, these types of chat companies are super easy, a simple js snippet on the page.
