It used to be that if your code ran quite quickly, a year later you could run it twice as fast for the same amount of money. These days, you’re much less likely to get a chip that’s twice as fast, but you may get one with twice as many cores. If your code is highly parallel, you can just spread it out a bit more...(via Mickaël Rémond)
Two features of Erlang, both of which are built into the language, make it especially suited to writing scalable applications: process creation and message passing.
Some years down the road, people will realize *this* model is service-oriented. There will be some kicking and screaming along the way, no doubt.