News for hackers. Stuff that matters.
Re:The Road to 2M Websocket Connections in Phoenix (2015) by rajeemcariazo on Sunday December 25, 2016 @12:22AM (#13253083)
Who is using Phoenix Framework in production?
Re:The Road to 2M Websocket Connections in Phoenix (2015) by willyk on Sunday December 25, 2016 @01:03AM (#13253168)
These companies are: http://bleacherreport.com/ https://www.brightcove.com/en/ http://cargosense.com/ https://www.inverse.com/ Apple has listed it in the stack in some job descriptions over the last year
Re:The Road to 2M Websocket Connections in Phoenix (2015) by anamoulous on Sunday December 25, 2016 @03:00AM (#13253423)
What benefit does Elixir provide to content companies (50% of these examples) given the low technical requirements of their product?
Re:The Road to 2M Websocket Connections in Phoenix (2015) by metabren on Sunday December 25, 2016 @04:50AM (#13253576)
I think I remember a Bleacher Report engineer talking about this on an Elixir podcast. They use it to power their push notifications and pride themselves in being consistently the fastest among their competitors.
Re:The Road to 2M Websocket Connections in Phoenix (2015) by amorphid on Sunday December 25, 2016 @01:12AM (#13253189)
Not Phoenix specifically, but here's a growing list of companies that use Elixir.

https://github.com/doomspork/elixir-companies/

Re:The Road to 2M Websocket Connections in Phoenix (2015) by ShaneWilton on Sunday December 25, 2016 @12:49PM (#13254819)
Tinfoil Security! All of our release engineering is orchestrated through a small Phoenix app that calls out to docker images to perform various types of deployments (Heroku, EC2, ECS, building docker images, etc).

I'll probably do a write-up on it at some point, because it is now trivial for anyone on the team to deploy any of our services to any environment (or a new one!), and to integrate new services into the platform.

Re:The Road to 2M Websocket Connections in Phoenix (2015) by skrebbel on Sunday December 25, 2016 @01:17AM (#13253201)
We do at TalkJS (https://talkjs.com). It's a pluggable user-to-user messaging service, and the concurrency that Phoenix and notably Elixir offer have been really helpful in keeping our infrastructure simple.
Re:The Road to 2M Websocket Connections in Phoenix (2015) by AtroxDev on Sunday December 25, 2016 @11:57AM (#13254658)
Changelog.com is using Phoenix. They also recently gone open source: https://changelog.com/posts/changelog-is-open-source
Re:The Road to 2M Websocket Connections in Phoenix (2015) by ghayes on Sunday December 25, 2016 @01:09AM (#13253180)
Postmates [0] for a variety of internal services. It's been rock solid and easy to ramp new team members on to. We do have a good number of in-house erlang folk, too.

[0] https://twitter.com/postmatesdev/status/803775289713049600

Re:The Road to 2M Websocket Connections in Phoenix (2015) by danso on Sunday December 25, 2016 @12:58AM (#13253152)
Re:The Road to 2M Websocket Connections in Phoenix (2015) by iagooar on Sunday December 25, 2016 @01:12AM (#13253188)
Me. Feel free to ask me anything.
Re:The Road to 2M Websocket Connections in Phoenix (2015) by babyrainbow on Sunday December 25, 2016 @03:09AM (#13253433)
How good is the "dynamic but functional and immutable" nature of the language good at catching potential bugs?
Re:The Road to 2M Websocket Connections in Phoenix (2015) by ghayes on Sunday December 25, 2016 @07:14AM (#13253865)
The immutable nature helps with 1) reasoning locally (you can always understand exactly what happens in a function by reading the function itself) and 2) debugging. Additionally, dialyzer provides a very nice (optional) typing system for erlang / Elixir.
Re:The Road to 2M Websocket Connections in Phoenix (2015) by _asummers on Sunday December 25, 2016 @10:57AM (#13254463)
And with the new deprecation in 1.4 of bare words, a disambiguation goes away where when looking at a function you sometimes had to go "is this a variable or a function". Now functions with 0 args have parens, always.

I've found the locality of everything in the function that you mentioned helps IMMENSELY in refactoring. Just give a function a namespace and call it, and then figure out where it actually belongs later as you figure out your implementation.

Re:The Road to 2M Websocket Connections in Phoenix (2015) by _asummers on Sunday December 25, 2016 @01:13AM (#13253190)
Us as well, I'll answer what I can!