Timeline for What makes Erlang suitable for cloud applications?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 10, 2012 at 11:38 | comment | added | Jörg W Mittag | Yes, sorry, I should have been more clear: cloud computing is distributed pretty much by definition, and it is often (not always but usually) implemented by clusters of inexpensive and more importantly unreliable machines but designed to deliver a reliable service. That's what makes Erlang such a good fit. | |
| Sep 10, 2012 at 11:33 | comment | added | pap | @JörgWMittag As long as we're splitting hairs... yes, it's purpose was to achieve fault tolerance. It achieved this through parallelization. It was designed to implement this in the AXE digital telephony switch which carried two isolated, parallel calculation pipes with one working as hot standby. | |
| Sep 10, 2012 at 11:28 | comment | added | Jörg W Mittag | Erlang was designed for fault-tolerant computing. It's just that distributed computing is a prerequesite for that (how can you reliably return a result if someone accidentally spills coffee over your single machine, you need at least two machines) and parallel and concurrent computing are just special cases of distributed computing, so Erlang also happens to be good at those. But that's not what it was designed for. | |
| Sep 10, 2012 at 11:25 | history | answered | pap | CC BY-SA 3.0 |