Backend: Java (phasing out), Go (phasing in), Postgres, Redis, all on Ubuntu EC2's. Frontend: JS (TypeScript/ES6), React, ReactNative, SASS, all Webpack'ed (except RN). I think it's a fairly light stack but am happy with it. I would use this as the starting point for pretty much every project.
I love Go, but always feel it is not very productive for web app backends. What about you ? Do you use an ORM w/ Go?
Also I'm more of a custom approach person which makes me very productive with Go. It's allows me to have laser focus on my needs instead of hooking up and reading docs and every little integration feature the framework has. And in result, I don't have dependency on a monolithic framework which could very well break everything in it's next release.
And finally, Go will build to binary for any-platform. So I can pre-build for the ARM processors, or Linux, or whatever else on Windows and just ship the binaries for server updates instead of managing make scripts and dependency resolution and blah blah blah. And if I wanted to I could sell the API "program" and sleep a little better about the IP contained in it (yes I know de-compilers exist). I could do this with C++ as well, but that's a whole 'nother ball game when it comes to tracking down memory leaks and segfaults.