Very nice article, I guess with movement to Cloud Services Model, it makes much more sense for…
dharmvir singh
1

I don’t see this way. Assuming that takes more time to write code in Go than other more popular choices, it seems as an optimization of machines, not of people.

You will not rewrite your ERP in Go, but maybe your load balancer. Maybe your workflow scheduler too.

Only things that suffer from high latency, parallelism or resource usage. Then balance with the increased development cost and time of Go. Only the usages that passed this 2 filters should be targeted to Golang for now, in my opinion.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.