Go + Websocket or NodeJS + Websocket?

Good day.
On synthetic tests, working with websockets on the Go will happen much faster and with minimal overhead. But the chat (like jivosite) more likely to choose node is for backend. Tell me, please, what can be justified that choice? Specialists, like, enough for both languages. Or the nodes have some considerable advantages, in comparison with th?
June 7th 19 at 15:00
4 answers
June 7th 19 at 15:04
Go and no synthetic tests faster.
as far as I remember to go and chat was the port Socket.IO
in the backend go the only thing that You need.
June 7th 19 at 15:02
two languages vs. one language

Go + Websocket -> you need a programmer or two, or one, but knowledge of both languages
NodeJS + Websocket -> enough of a JS programmer
What is good about these two, so the fact that they are the most imprisoned under the microservices architecture.
In General, it is necessary to look what functions are needed. Languages JS, Go, Python, suitable for writing microservices.
RebbitMQ helps it all work together. Have to go out from that what the problem. Go good for parallel math. There are ready solutions in the field of blockchain. Node does not Go worse, just need to produce processes and not to overload them as They are single-threaded. that is, load balancing. - Pansy.Fe commented on June 7th 19 at 15:05
June 7th 19 at 15:06
I think everything here is simple - money.
Developed on the Node will query X and developed on TH 2. And the code on the Gcd easier for most, even though a bunch of Kabakov.
And Soshnikov there are not so many here in a year or two to catch up.
June 7th 19 at 15:08
Overhead purely for the opening and maintenance of websockets not so significant compared to the resource consumption business logic which in my opinion is important ottalkivatsya not from performance but from the fact why would you even contacted websockets.

Find more questions by tags Node.jsGo