Harrisonl
Using Websockets for all communication - Good idea or bad?
I’m building a react/elixir web app (not server side rendered if it makes a difference) where currently all communication is done over websockets. Basically, a user connects to the socket, then over various different pages, joins and leaves different channels.
So far I haven’t seen any issues (currently in production - although it’s only me testing it) but not sure if I am missing something here.
Is there something I am possibly missing as to why this would be a bad idea?
Most Liked
Nicd
Two downsides I can think of offhand:
- No caching, the user’s browser and any intermediate network devices cannot cache WebSocket content.
- Bad for search engines. Some search engines crawl JS but I don’t think any of them will open WS connections to get your page content.
Whether these are problems or not depends on your needs.
wmnnd
Phoenix is perfectly capable of handling huge numbers of simultaneous websocket connections. You might find this blog post (which is already back from 2015!) insightful:
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
Courses that'll move you from confusion to "Aha, now I get it!"