May Sale! All accounts are 40% off this week.
I will real-time chat application. I have hesitations about which infrastructure to use for this.
1- Pusher 2- Realtime Database and socket.io (Firebase) 3- Livewire
I want it to be a healthy infrastructure for an average of 10 thousand people to use daily. It doesn't feel realistic to do it with Livewire, but the pusher is a little costly. How can I make a chat application that will consume minimum resources of the server for the use of approximately 10 thousand people per day? Do you have any suggestions?
If you have any other suggestions other than these solutions, I am looking forward to you, thank you in advance.
@moriarty You’ve got two choices: either set up and maintain the socket infrastructure yourself using something like Laravel Websockets; or pay someone like Pusher to take care of that for you.
Either way, there’s going to be a cost in setting up a server to act as your socket server, or paying a third-party to handle the infrastructure for you.
So, what is the stable option for the chat application that requires high level user participation?
I am unsure between paying Pusher and rising server costs. I am not sure which way it will be more suitable and stable, Thank you for the answer
@moriarty No one can answer that for you.
Do you or have someone on your team that can set up a web socket server and diagnose any issues if they occur…?
Unfortunately not, then the only option is pusher?
Well it just means if there’s an issue with your web sockets server, then it’s on you to resolve the issue and users won’t be able to chat until you do resolve whatever the issue is. So it’s up to you to decide whether this burden is worth saving the cost of something like Pusher.
Pusher takes care of maintaining web sockets servers for you, but obviously charges for this convenience.
Please or to participate in this conversation.