This is super light weight! But, not in a good way IMO. As much as I like the idea of giving freedom to the teams to build their Microservices with tools and l

This is super light weight! But, not in a good way IMO. As much as I like the idea of giving freedom to the teams to build their Microservices with tools and libraries that they want to use. In reality you usually end up to keep many low level parts similar in order to keep things easier to maintain and also easier to reorganize your developers on different teams. That's where light frameworks feel a bit short to me, unless you do an excellent job on knowledge and library sharing between different teams, which is almost impossible if you have many teams. That's why many large enterprises end up using Spring framework for their Microservices. It just gives you many things out of the box, and it's opinionated about many low level stuff. I'd probably choose go-micro or go-kit for doing Microservices in Golang.