What's the best library for network programming?

<p>Hi <a href="/r/golang" rel="nofollow">r/golang</a>,</p> <p>I&#39;m working on a project, making a framework for distributed programming. Obviously we need some communication between systems on a network. We&#39;ve used a similar framework in Java, where it utilised socket programmering to communicate between nodes on a network.</p> <p>I&#39;m asking here as I&#39;m fairly new to Golang and I don&#39;t want to waste too much time reinventing the plate if it&#39;s already out there in a nice library.</p> <p>Cheers</p> <hr/>**评论：**<br/><br/>StoneJolt: <pre><p>maybe something like <a href="http://www.grpc.io/" rel="nofollow">http://www.grpc.io/</a></p></pre>peterbourgon: <pre><p>Absent more information, a framework for distributed programming should probably not rely on another framework for its network communication. Use the stdlib, net.Dial, and net.Listen.</p></pre>ChristophBerger: <pre><p>Valid point - go with the stdlib as far as you can. </p> <p>Still, I am curious... is your point specifically about <em>frameworks</em> (I understand it this way), or rather about <em>any</em> 3rd-party lib/framework/whatever that should not rely on any other 3rd-party lib/framework/whatever? </p></pre>Shaqalac: <pre><p>That is indeed a very good point!</p></pre>Frakturfreund: <pre><p>Annother option is Google’s <a href="http://www.grpc.io/" rel="nofollow">gRPC</a>, which uses Protocol Buffers for data exchange. It has a <a href="http://www.grpc.io/docs/quickstart/go.html" rel="nofollow">Go Quickstart</a> tutorial.</p></pre>natefinch: <pre><p>If you&#39;re new to Go, I suggest just using the std lib&#39;s net/rpc</p> <p>There&#39;s no real reason to use anything more complicated.</p></pre>kfirufk: <pre><p>What about a message broker like nats.io? It&#39;s written in go.</p></pre>picklednull: <pre><p><a href="http://zeromq.org/" rel="nofollow">zeromq</a>. There are <a href="https://github.com/zeromq/goczmq" rel="nofollow">bindings for Go</a>.</p></pre>qu33ksilver: <pre><p>ZeroMQ is a great library for distributed network programming. Use this - <a href="https://github.com/pebbe/zmq4" rel="nofollow">https://github.com/pebbe/zmq4</a>. The latest v4 comes in ECC built in to the protocol.</p></pre>ChristophBerger: <pre><p>Have a look at <a href="https://awesome-go.com/#networking" rel="nofollow">Awesome Go</a> - but keep in mind that the stdlib already provides quite a lot - <code>net</code>, <code>encoding/gob</code>, <code>net/http</code>, <code>net/websocket</code>,... (as others have already pointed out here).</p> <p>There are also quite some libs and frameworks available for distributed programming, like micro, go-kit, and <a href="https://awesome-go.com/#distributed-systems" rel="nofollow">others</a>, so you might not even have to create your own.</p></pre>itsamemmario: <pre><p>You&#39;d be suprised how well developped the standard library is. That being said, <a href="https://godoc.org/golang.org/x/net/websocket" rel="nofollow">https://godoc.org/golang.org/x/net/websocket</a> or <a href="https://godoc.org/github.com/gorilla/websocket" rel="nofollow">https://godoc.org/github.com/gorilla/websocket</a></p></pre>shark1337: <pre><p>I&#39;d say net/http, but if you&#39;re not looking to support http2, you can use fasthttp library. There&#39;s a lot of web frameworks that implements the basic http package with some cool features, but I&#39;m not sure if you&#39;re gonna need all of those stuffs. If you&#39;re gonna make it to be distributed, you&#39;ll see that after using a big framework (only id), you&#39;ll realize that it comes with a lot of useless stuffs that makes your binary larger. I&#39;d go for net/http + http router, that&#39;s all I would use.</p></pre>