That's not to say they can't inhabit a lot of the same areas, but Go's area of interests will probably remain somewhat separate from Erlang.
https://news.ycombinator.com/item?id=5451916
https://news.ycombinator.com/item?id=7943248
But there are more here and there if you hunt for them.
I think for things where they are sort of similar, Go will definitely be the more successful language because it looks so much more familiar and because it's moving faster with more momentum, at this point.
I'm using Erlang for a semi-embedded thing at the moment, though, where stability is more important.
What I do see eating into Erlang is Scala and Akka, though.
On the other side of the coin, if I wanted to write a simple command line tool quickly that was easy to deploy to many servers, Go might be a great choice, where Erlang is a bit painful for small and simple programs.
Loïc Hogun (author of Cowboy, other projects) said:
As Go gains libraries like groupcache will it become more and more go-to for networked and shared systems?Is Go moving up from concurrent to fault-tolerant in a real way?