4 ms·

Here is something that I have been toying with, please downvote me if you guys think this is out of place: Why do you need so much fault tolerance and concurre

Here is something that I have been toying with, please downvote me if you guys think this is out of place: Why do you need so much fault tolerance and concurrency? It seems to me that the regular server would only need to thread a little bit, process incoming requests, and shoot out responses. (this is assuming you're not building MySQL or a heavy duty web server)

jhancock 17y ago
"this is assuming you're not building MySQL or a heavy duty web server" erlang is for building heavy duty web servers. It scales down pretty well too, but there is still a learning curve.
oomkiller 17y ago
Lots of people starting to use Erlang needs fault tolerance for high availability, and high concurrency because they need to scale massively. YAWS, one of the more-popular webservers written in Erlang (that has docs, unlike Mochiweb), blows Apache out of the water when it comes to serving many users (http://www.sics.se/~joe/apachevsyaws.html http://www.sics.se/~joe/apachevsyaws.html). Apache can serve about 4,000 parallel sessions on the same hardware YAWS can serve at least 80,000 parallel sessions. This is due to the high level of concurrency that Erlang enables and encourages. Another example is ejabberd, one of the most popular Jabber/XMPP servers. It takes advantage of the high concurrency also, which allows is to process many more connections than Openfire or the C-based jabberd and jabberd2.