Network Programming with Go: Code Secure and Reliable Network Services from Scratch

Adam is obviously an expert in Go and networking, and his Go code shows it. I am working my way through the book now, and it is really excellent! The networking part shows his expertise in networking, and the examples have lots of little extras. Like using io.MultiReader to do a lookback on a stream (on page 83). The type-length-value example (pages 79-86) could be used instead of GRPC for simple applications. Or like implementing heartbeats at the app level (pages 68-70) instead of using TCP keepalive. Application-level heartbeats will still work regardless of firewall rules, when keepalive could be blocked. Sheeze! Do you folks have any idea how cool and important that stuff is, and how much easier the Go networking library makes it? Kudos to Adam. Thank you for spending your valuable time trying to educate Go programmers! Ignore the complainers; they don't know a jewel when they see it.

Thanks for the trip down memory lane, but that's not what I asked for when I bought a book on >>Go<< networking. The book itself concedes the waste of time the author is dishing out: "Although OSI is less relevant today than it once was...". Yeah, OSI is a product of the 1970's and news flash - Go handles ALL these concerns for us. One need not putter around in the cobwebs of EBCDIC to make an HTTPS server in Golang!I suspect this chaff is purposefully added to make readers feel they got value for their money. I suggest prospective purchasers read the "OSI model" entry on Wikipedia and buy something else. 2 stars instead of 1 because the author eventually gets to the point after putting you to sleep a few times.

This book has upped my go game quite a bit: Certificate pinning for https clients, breaking free of non-standard lib packages for my http handlers, running go progs via Unix sockets, and introducing just how simple it is to setup gRPC server/clients are just a few of the things I learned.I want to emphasize again how awesome it is Adam uses standard lib, especially net/http for building a mux/server. Go search "build a server with go" and you'll find nearly every time they introducing a single endpoint handler before introducing the third party package to handle mux routing.Still haven't read some of the earlier chapters, but so far this book has been great.

I like the quality of writing in the book so far. I've only read 3 chapters. But I can't say I like the example programs given here at all. They are all pretty pointless because they are supposed to teach you network programming, but they are not even of any practical use. They are in the form of Golang tests, that just "pass". What's even the point of that? Ideally, I would have preferred a bit of code you put in a client machine and some code you put in a server (maybe running in a local container) so you can see something happen. In any case, nostarch has created a really high-quality book, that I personally find to be a very pleasant reading experience. I like this book but the process of trying to get some satisfaction out of it is giving me a headache.

This is a great book! I'm using it alongside "The Go Programming Language" and "Learn Go with Tests" as stepping stones toward reading "Distributed Services with Go" by Travis Jeffery.Woodbeck's book is a great introduction to Go's Network Programming toolbox and it was easy to follow while writing the examples in an editor. I recommend it if you're interested in learning about web services and networking tools in Go.

This book is a beginner book on Go with a couple of basic chapters on networking thrown in at the beginning. Given the title, I was expecting to learn the concepts behind networking on Go, not simply just use the network libraries already inclusive in the language.