Companies using Elixir
PagerDuty uses Elixir extensively. Here’s a list of articles and talks where they talk about their use of it:
- Elixir at PagerDuty blogpost from Cees de Groot.
- How I Centralized Our Scattered Business Logic Into One Clear Pipeline For Our Elixir Webhook Service blogpost by Michael Viveros.
- ElixirConf 2019: Elixir + CQRS - Architecting for Availability, Operability, and Maintainability At PagerDuty - Jon Grieman
Elixir’s our primary language, and has been for some time now. There’s still some older services predating our choice of Elixir, but less and less of them as time goes on and things are replaced. Outside of special cases like our mobile client apps, I don’t believe there’s any team in engineering that doesn’t work with Elixir on a frequent, if not exclusive, basis.
The entire backend of Discord runs on Elixir (with some performance-critical pieces in Rust 1). Their CTO has written that if they had to go back and start over, they would definitely choose the same path again 2, and he’s not the only one with that sentiment. 3
Here’s a list of articles where they talk about how they’re using Elixir:
- How Discord Scaled Elixir to 5,000,000 Concurrent Users
- Using Rust to Scale Elixir for 11 Million Concurrent Users
- How Discord handles push request bursts of over a million per minute with Elixir’s GenStage
Heroku’s router is written in Erlang 4.
The Vault team was first to use Elixir inside Heroku 5. Their team is responsible for licensing and financial services, such as invoicing, credit card payments, etc. Most of their services are used internally at Heroku.
Around 2018, Heroku’s front-end team also began using Elixir 5. The team has 21 engineers: about 4 of them doing Elixir full-time, and 8 engineers altogether doing Elixir here and there. They continue using Elixir because they feel productive and happy with it. They have also found it is an easier language to maintain compared to their previous experiences.
Metrist builds an observability tool that functionally tests and monitors cloud products (like AWS, Azure, Stripe) as well as IT-related tools (Zoom, Jira) and general SaaS-style vendors (Stripe, Humi). From a range of actions, like looking at status pages, actively monitoring APIs, and observing how our customers’ production systems interact with them they try to distill a summarized status so their users know first when something is amiss with any of their vendors.