Skip to content
0:00 / 0:00

#elixir#phoenix#pubsub

ElixirConf 2017 - Cajoling the Bird: How we squeezed more out of Phoenix PubSub- Simon Zelazny

ElixirConf

13K subscribers • 28 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Simon Zelazny
  • May be out of date. Uploaded 9 years ago, in an area where tools change fast.

Advanced. Deep dive for people who know the field.

2.5K views9 years ago2 recommendations

Web developmentDistributed systemsElixir and ErlangScaling and large-scale architectureWeb performance

Simon Zelazny shares how Grindr optimized and scaled Phoenix PubSub to handle massive concurrent user loads.

The uploader added no description.

Why it's here

2 people recommend this

What people say. Recommended for engineers looking to scale Phoenix channels and PubSub to millions of concurrent users.

u/Merotoroin r/elixir • Recommends

On “What makes Elixir—and Phoenix Channels—faster/more efficient than, say, Socket.IO?”

your use case sounds similar to what grindr does. link to this video i also don’t know much about these technologies, just wanted to share more info, you might find what makes phoenix so efficient in that video. here’s advice you didn’t ask for: don’t optimize at this point. sounds like you’re starting out with that project. your solution sounds adequate for this time and you can probably keep it for a while until it doesn’t fit your needs. if your user base grows by an order of magnitude and you don’t need to adjust your architecture to fit the new scale it’s a sign that you probably over-engineered your solution. that being said, if you’re never coming back to this project and you need unlimited…

u/murderous_ragein r/elixir • Recommends

On “How Discord Scaled Elixir to 5,000,000 Concurrent Users”

Simon Zelazny from Grindr did a great presentation at ElixirConf 2017 in Bellevue on a similar topic that I really enjoyed: link to this video