Apache Thrift vs Erlang: What are the differences?
What is Erlang? 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.
Apache Thrift belongs to "Serialization Frameworks" category of the tech stack, while Erlang can be primarily classified under "Languages".
Apache Thrift and Erlang are both open source tools. Erlang with 7.7K GitHub stars and 2.09K forks on GitHub appears to be more popular than Apache Thrift with 6.42K GitHub stars and 2.94K GitHub forks.
According to the StackShare community, Erlang has a broader approval, being mentioned in 70 company stacks & 45 developers stacks; compared to Apache Thrift, which is listed in 10 company stacks and 8 developer stacks.
What is Apache Thrift?
What is Erlang?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Apache Thrift?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Apache Thrift?
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).