There's no need to involve Go in that stack if you're building on Elixir. If you absolutely need interop with something else it'd be better to go with something

There's no need to involve Go in that stack if you're building on Elixir. If you absolutely need interop with something else it'd be better to go with something more focused (either on speed, correctness or something else, as Go doesn't really focus on much of anything, except design-wise) and use it through ports or the like, from the BEAM. Go as an addition to a BEAM app won't add anything as it mostly does nothing much better than the BEAM and what it does better will be better handled by other languages. Some people would attempt to make a case for it being able to spawn threads, etc., but its scheduling makes in inherently as incompatible with the BEAM as any other language, so it's not a reasonable point to make.