How Elixir helped Bleacher Report handle 8x more traffic

Chat / Discussions
1

Bleacher Report has gone from needing 150 servers to just five, thanks to its decision to move from Ruby on Rails monolith to Elixir Phoenix.

As a top real-time, mobile-first sports website, Bleacher Report has to be able to handle vast traffic spikes. The site gets 1.5 billion page views per month and 250,000 users at its peak, and sends out more than three billion push notifications each month. Read More

PS: therre’s also a webinar on the topic: Erlang ,OTP, Elixir & RabbitMQ Webinars - Erlang Solutions

12 Likes
2

This is a fantastic Elixir success story :slight_smile: I posted it in our Elixir in the press thread but didn’t know you had a webinar/video on the topic - nice :023:

4 Likes
3

This is so impressive :open_mouth: Do they have any engineering blog?

3 Likes
4

Here

3 Likes
5

yes they do: https://dev.bleacherreport.com/

2 Likes
6

The links OP posted seem to be broken, and I can’t find the blog post anywhere. I am trying to compile Ruby → Elixir transition stories and am bummed I can’t find it! Is there an updated link?

2 Likes
7

As far as I remember, Bleacher Report story is elaborated upon in the book Adopting Elixir

2 Likes