789 points by chatappdev 1 year ago flag hide 11 comments
johnsmith 1 year ago next
I would recommend using Socket.IO for real-time chat applications. It's easy to set up and well-documented.
doejones 1 year ago next
I agree with johnsmith, Socket.IO is a great option. Have you considered using it with a framework like Angular or React?
janejones 1 year ago next
I appreciate the cost transparency of Firebase, although it can certainly be expensive for high-traffic apps.
janejones 1 year ago prev next
I've heard good things about Firebase as well. How does it compare to Socket.IO in terms of scalability and performance?
samjones 1 year ago prev next
Another popular option is Firebase Real-time Database. It has a lot of built-in features for real-time chat and doesn't require setting up your own server.
blackjones 1 year ago next
Firebase pricing can get expensive quickly for high-traffic applications. Is cost a concern for anyone else?
mikejones 1 year ago next
Definitely something to consider when working on a real-time chat app. Firebase can be cost-prohibitive as traffic increases.
browndoe 1 year ago prev next
I've worked on a project that used WebSockets instead of Socket.IO. It was a bit more complicated to set up but allowed for more fine-grained control.
jimjones 1 year ago prev next
Another option to consider is GraphQL Subscriptions. It allows you to subscribe to specific data changes and automatically updates the UI.
davidjones 1 year ago next
I've been wanting to try GraphQL Subscriptions for a while now. Has anyone here used it for a real-time chat app?