Erlang vs Julia: What are the differences?
Developers describe Erlang as "A programming language used to build massively scalable soft real-time systems with requirements on high availability". Some of Erlang's uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance. OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. On the other hand, Julia is detailed as "A high-level, high-performance dynamic programming language for technical computing". Julia is a high-level, high-performance dynamic programming language for technical computing, with syntax that is familiar to users of other technical computing environments. It provides a sophisticated compiler, distributed parallel execution, numerical accuracy, and an extensive mathematical function library.
Erlang and Julia belong to "Languages" category of the tech stack.
"Real time, distributed applications" is the primary reason why developers consider Erlang over the competitors, whereas "Lisp-like Macros" was stated as the key factor in picking Julia.
Erlang and Julia are both open source tools. Julia with 22.7K GitHub stars and 3.43K forks on GitHub appears to be more popular than Erlang with 7.74K GitHub stars and 2.1K GitHub forks.
WhatsApp, Heroku, and thoughtbot are some of the popular companies that use Erlang, whereas Julia is used by inFeedo, Platform Project, and N26. Erlang has a broader approval, being mentioned in 70 company stacks & 47 developers stacks; compared to Julia, which is listed in 5 company stacks and 5 developer stacks.
What is Erlang?
What is Julia?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Erlang?
What are the cons of using Julia?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Postmates built a tool called Bazaar that helps onboard new partners and handles several routine tasks, like nightly emails to merchants alerting them about items that are out of stock.
Since they ran Bazaar across multiple instances, the team needed to avoid sending multiple emails to their partners by obtaining lock across multiple hosts. To solve their challenge, they created and open sourced ConsulMutEx, and an Elixir module for acquiring and releasing locks with Consul and other backends.
It works with Consul’s KV store, as well as other backends, including ets, Erlang’s in-memory database.
Another major decision was to adopt Elixir and Phoenix Framework - the DX (Developer eXperience) is pretty similar to what we know from RoR, but this tech is running on the top of rock-solid Erlang platform which is powering planet-scale telecom solutions for 20+ years. So we're getting pretty much the best from both worlds: minimum friction & smart conventions that eliminate the excessive boilerplate AND highly concurrent EVM (Erlang's Virtual Machine) that makes all the scalability problems vanish. The transition was very smooth - none of Ruby developers we had decided to leave because of Elixir. What is more, we kept recruiting Ruby developers w/o any requirement regarding Elixir proficiency & we still were able to educate them internally in almost no time. Obviously Elixir comes with some more tools in the stack: Credo , Hex , AppSignal (required to properly monitor BEAM apps).
This language and its community are exactly how I have always dreamed them to be. The language is both easy to use/very flexible/powerful and very fast ! The community is very dynamic, open minded and ambitious.
Fast development and fast execution time. Flawless communication between packages.