Elixir and the Internet of Things – Handling a Stampede

Glad to see more Erlang/Elixir/OTP articles on HN. With all these newfangled cool kid concurrent languages, people seem to have forgotten the sophisticated, decades old solution. Funny to think telecoms were solving a lot of the same problems web devs are now (High Availability, Low Latency, Fault Tolerance, large amounts of concurrent connections).

The funny thing is that most people choose Elixir over Erlang because of the syntax - personally I can&#x27;t stand Ruby but love the Erlang syntax. When I see Erlang code, everything just clicks - almost like I&#x27;m reading prose.<p>So, if you want to harvest the power of Erlang, I&#x27;d suggest you start with the real thing first. The only drawback is that once you get used to functional programming, guards, pattern matching, OTP, cheap processes, links and all the other goodness, there&#x27;s no way back.<p>If you still feel Erlang is weird after spending a couple of days working with it, feel free to jump on the Elixir bandwagon. :)

I only skimmed so far, but you might want to checkout Ranch instead of rolling your own tcp acceptor pool, <a href="http://ninenines.eu/docs/en/ranch/HEAD/guide/" rel="nofollow">http:&#x2F;&#x2F;ninenines.eu&#x2F;docs&#x2F;en&#x2F;ranch&#x2F;HEAD&#x2F;guide&#x2F;</a>

This seems pretty neat but what advantage does this have compared to terminating SSL at nginx? I guess you still need to have something that nginx can hand the connections off to.

Oooh, I didn&#x27;t even know this existed. I&#x27;ve always been curious about learning Erlang, but I&#x27;m always suspicious of languages that predate the vowel generation.

Gripping article, but his incorrect use of apostrophes made me want to an hero.