I have been rereading Frank Herbert's Dune so when I read this interesting article, I thought it could have also been titled "A Historical Who's Who of Mentats." I am definitely looking forward to Parts 2 through N...
There are several blog posts out there on the Go vs Rust debate and how both languages are not really in the same boxing weight class, so to speak, but people tend to compare and contrast the two languages more often because they both launched around the same time. With that said, I'll take a crack at this question... Without having to define what "large amount" means to you or others, I would guess you want to pick Rust. Go uses a runtime to perform garbage collection; while Rust is not runtime-based (no garbage collection), and manages memory with zero-cost abstractions and a very strict compilation process. So, if you're turned off by your applications being attached at the hip to a garbage collector that will cost precious milliseconds, then Rust is a better choice. It's also a better choice for having more advanced language features than Go. Rust is a LLVM-based language so I believe Rust can target more platforms than Go, but Go has a better story for easier cross-compilation right now. However, one of the Rust team's goals for 2018 will be focusing on easier cross-compilation.
If the article is meant to walk someone through creating their own microservice, it begins to miss crucial code snippets in the `Accepting POST Requests` section. It doesn't point out that one should go back to the Cargo.toml file and add the `url` and `serde_json` crates (and possibly `serde` and `serde_derive`). Also, it's missing these crates in the point regarding updating the `use` statements. However, if the article is not meant to walk the reader through creating their own, but just to follow along from your git repository, then think about updating the article to have the repo url listed at the beginning. Good article, otherwise.