When is it better to use WebSockets instead of regular HTTP for talking between our internal services?
Mateo Ramirez
·491 views
Hey everyone, I've been thinking about how our internal services talk to each other, especially for stuff that needs super fast updates or an always-on connection. We usually just use HTTP, and that's totally fine for a lot of our request/response needs. But for things like live dashboards, getting immediate alerts between services, or even checking on long background jobs, I'm wondering if WebSockets could be better. It seems like they could cut down on all that constant checking and speed things up. So, what have folks seen work well? And what are the pros and cons? When do you think the extra hassle of setting up and keeping track of WebSocket connections is actually worth it internally, instead of just polling HTTP more often or using server-sent events?
7 comments