Crystal vs Erlang: What are the differences?
Developers describe Crystal as "Fast as C, slick as Ruby". Crystal is a programming language that resembles Ruby but compiles to native code and tries to be much more efficient, at the cost of disallowing certain dynamic aspects of Ruby. On the other hand, Erlang is detailed 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.
Crystal and Erlang can be primarily classified as "Languages" tools.
"Compiles to efficient native code" is the top reason why over 27 developers like Crystal, while over 49 developers mention "Real time, distributed applications" as the leading cause for choosing Erlang.
Crystal and Erlang are both open source tools. Crystal with 13.5K GitHub stars and 1.05K forks on GitHub appears to be more popular than Erlang with 7.74K GitHub stars and 2.1K GitHub forks.
According to the StackShare community, Erlang has a broader approval, being mentioned in 70 company stacks & 47 developers stacks; compared to Crystal, which is listed in 7 company stacks and 14 developer stacks.
What is Crystal?
What is Erlang?
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?
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).
i leaving php, node, and python cause i have a new love, crystal