is your service connecting to 3rd party websocket services, or is your service the web socket server?

N/A

I might be a bit blind

Anyways, my project just uses websockets to update data in real time on the client side

then the bottleneck would be your code

I haven't had any problems yet, i was just wondering how to future proof it

And would it consume a lot of resources on the hosting side

write efficent code, and that will both future proof it and take less memory

That's probably the best advice i can get

Golang is a good choice btw

Ty for the help since it did make me think about which parts i need to fix

It always is

I've been told it's easy to learn

Yup and it's somewhat hard to write inefficient code in it

I mean, you still can, however it's not as easy to do that as in js, for example

Wasn't really my choice to work with js but I was forced to use it

As for golang I've never worked with it

Note + Follow up on this thread:
I've been using an express server with socket.io and it works great as long as the connection is relatively short (less than 30min), after-which your Network Egress explodes and requests become extremely slow.

Let me know if there's a solution for this? I am thinking of using an external socket server just for this use-case.

i would have to recommend you setup tracing so that you can have data on what is "slow"

Could it be caused from a surplus of connections and memory buildup? Were you able to fix it?