# Just a silly topic about Go lang and Elixir lang **URL:** \ **Category:** Users\ **Created:** [October 27, 2017, 3:27am UTC](https://discuss.dgraph.io/t/just-a-silly-topic-about-go-lang-and-elixir-lang/1892 "2017-10-27T03:27:24Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\ **Post date:** [October 27, 2017, 3:27am UTC](https://discuss.dgraph.io/t/just-a-silly-topic-about-go-lang-and-elixir-lang/1892/1 "2017-10-27T03:27:25Z")
Elixir uses technology with more than 30 years in the telephony market. Developed by Ericsson. It has advantages of being able to scale in any direction “out of the box” (vertical, horizontal). It recovers crashed processes “on the fly” (supervisors) without having to restart the program completely. It supports GraphQL (third party). Has native Analyzers - Where you can see problem processes consuming resources and so on. The processes talk to each other. Uses all cores of a CPU. And several advantages (like syntax, PubSub). I was seeing another day comparisons of applications created in Go-Lang with others made in Elixir. I found the performance behind the benchmarks interesting. 2 millions conections at tha same time. With 450ms latency. (correct me if I’m wrong) Would it be interesting to consider adopting Elixir instead of Go lang as core base (Client) for the Dgraph? Elixir is very simple to adopt and maybe the amount of helpers for the Dgraph project would grow. Like I said, Just a silly topic. Cheers. REF: [https://youtu.be/Toluc5MCQWs](https://youtu.be/Toluc5MCQWs) --- _[View the full topic](https://discuss.dgraph.io/t/just-a-silly-topic-about-go-lang-and-elixir-lang/1892)._