Go performance from version 1.2 to 1.18

Re:Go performance from version 1.2 to 1.18 by tgtweak on Friday February 04, 2022 @12:30PM (#30209808)

For us it's as simple as docker build right from the repo -> push to registry for test deployment then tag with prod for rollout from there.

Probably not ideal for 20+ dev teams or high complexity deployments but this is the simplest CI and its much quicker build than node, so dev's can do it locally in all cases.

[ Parent | on HN ]

Re:Go performance from version 1.2 to 1.18 by throwaway894345 on Friday February 04, 2022 @01:46PM (#30211149)

Yeah, this is fine for early stage startups, but eventually you don't want developers to deploy directly to production.

[ Parent | on HN ]

Re:Go performance from version 1.2 to 1.18 by Abishek_Muthian on Friday February 04, 2022 @09:50PM (#30216616)

Very interesting, Can you give some specific examples of where CI/CD tools which works fine for large organizations for other programming languages don't work to your satisfaction with Go?

[ Parent | on HN ]

Re:Go performance from version 1.2 to 1.18 by throwaway894345 on Saturday February 05, 2022 @11:19AM (#30222574)

I think you’ve misunderstood the thread. I was arguing that you can get away with “dev builds image locally and pushes straight to prod” in an early startup, but in a mature organization you need CI/CD.

[ Parent | on HN ]

Re:Go performance from version 1.2 to 1.18 by Abishek_Muthian on Saturday February 05, 2022 @09:44PM (#30228805)

I think I got that part correctly,

> My only grievance with Go in the cloud is that it's tedious to have to set up a CI job or similar to build your binaries to deploy in your functions.

So I thought your CI/CD works to your satisfaction for other programming languages, But you found Go tedious and so I wanted to understand some specific cases.

[ Parent | on HN ]