All of the upsides for microservices the author enumerates are really luxuries that may or may not be afforded a harried team trying to beat their next deadline, which they're having trouble doing because they're slowed down due to the use of microservices. This isn't hypothetical; I've been on that team before.<p>I'm not saying microservices are bad, or good. There are tradeoffs, and in the situations I've been in, the negatives outweighed the positives, largely because the architecture was forced on us without providing the resources - mainly time - to do it right.
Started talking about Go, so I'm going to write my own article about micro-services in this comment.<p>It goes like this:<p>Micro-services, sometimes good.