What is your local market tells you about the usage of Go language? Do they ask for it via job ads or prefer much more traditional technologies, such as Java or something alike?
Last time I had a conversation with a couple of companies I keep in touch (a couple of months ago), we had a long discussion about their choice to migrate their backend services originally implemented in Go, to re-implement them either in Java or (modern) C++, after the telemetry fiasco [1] that is going to be added in future release of Go inside their toolchain.
They told me they cannot risk it, be it opt-in or opt-out, it does not matter for them, because Google any time it wants can make it mandatory, and as a financial institution with high competition, they cannot risk it; that's what they said to me, not my words.
So...would I use it nowadays? Absolutely not.
Should you stay with a much more traditional tech stack, such as Java? Yes, of course, especially now with the release of OpenJDK 21 that will introduce virtual threads that more or less behave like Go's goroutines.
Last time I had a conversation with a couple of companies I keep in touch (a couple of months ago), we had a long discussion about their choice to migrate their backend services originally implemented in Go, to re-implement them either in Java or (modern) C++, after the telemetry fiasco [1] that is going to be added in future release of Go inside their toolchain.
They told me they cannot risk it, be it opt-in or opt-out, it does not matter for them, because Google any time it wants can make it mandatory, and as a financial institution with high competition, they cannot risk it; that's what they said to me, not my words.
So...would I use it nowadays? Absolutely not.
Should you stay with a much more traditional tech stack, such as Java? Yes, of course, especially now with the release of OpenJDK 21 that will introduce virtual threads that more or less behave like Go's goroutines.
That's just my honest opinion, that's all.
[1] https://github.com/golang/go/issues/58894