Go performance from version 1.2 to 1.18
The thing people don&#x27;t seem to appreciate&#x2F;understand with go is the effects of using it in serverless and cloud native environments.<p>Every high throughput service I&#x27;ve had moved to GO has used a tiny amount of Memory and CPU compared to the implementation it replaced, typically nodejs, python, Scala and .net.<p>In a cloud world where it&#x27;s usually boiled down to pay-per MB of in-process memory and per cycle... That can be 4-5 figures a month in reduced cloud cost for the same traffic.<p>Tiny output binaries are also very quick to transfer and spin up in serverless as well - often reducing costs further.<p>The benefits over time of essentially knowing things will get faster with each new version is really encouraging as well. Imagine your cloud bill went down over time as a result of simply rebuilding your service on newer golang core and redeploying.