What’s the best option for websocket functionality in a scalable app?

0
0
Asked By CuriousCoder88 On

I'm building an MVP for a project that will rely heavily on concurrent websocket connections. As the app grows, I need to manage a scalable number of connections efficiently. I know managed services like Pusher are user-friendly, but I'm worried about costs as I expand, especially since this is a bootstrapped project. If you were in my shoes and looking for a budget-friendly yet scalable solution, what would you choose or recommend?

3 Answers

Answered By ElixirEnthusiast On

If you are considering a custom backend, I’d recommend looking into Elixir and Erlang. They can handle millions of concurrent connections efficiently and can be quite cost-effective, around a few hundred bucks a month. Plus, if you’re familiar with Ruby on Rails, the transition might not be as rough as you'd think.

Answered By TechieTommy On

First off, consider whether you *really* need websockets. Sometimes server-sent events (SSEs) might do the trick without the extra overhead. They’re easier to handle for certain use cases if you’re looking for something straightforward. Just make sure your provider supports them well, as not all do.

Answered By RNerdy99 On

While Elixir offers great scalability, I’d suggest weighing the learning curve if you’re switching from Ruby. Have you ever worked with Elixir in production? It might be a great choice, but just be prepared for the transition if you go that route.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.