Sergey Kirichenko

Thank you for the comment. We would argue that go gives you only benefits in the size of the artifacts and resources usage footprint. Go has different philosophy and require different approach to write application. For example, if you try once to write concurrent solution in go you would see how ease it is in comparison to java. Though, we completely agree, there is no obvious winner as there is no silver bullet solution. At the end of the day the set of architecture/languages/frameworks you choose to make it work for you is a right choice.

Thank you for the comment. The purpose of the article was not to find the most performant solution but rather to identify the issue that was causing go solution in the original test to fell behind the java solution. Though we like your idea to cover more in depth both Java and Go solutions. We might reconsider to write another article to compare all possible java and go solutions to write rest services and measure both performance and resource usage.