Archive for May 2nd, 2008
-
Reliability
Steve Vinoski talking about reliability (in particular my favourite: Erlang)
To achieve reliability, you have to accept the fact that failure will occur, Once you accept that, then other things fall into place: you need to be able to restart things quickly, and to do that, processes need to be cheap. If something fails, you don’t want it taking everything else with it, so you need to at least minimize, if not eliminate, sharing, which leads you to message passing. You also need monitoring capabilities that can detect failed processes and restart them
Amen to that!
Technorati Tags: reliability, Erlang
Most Popular
- Google Big Table paper (3)
- Google sucks! (3)
- July 29 2007 (3)
- Setting up Subversion on my webhost (2)
- July 23 2007 (2)
- Thankgod for chaos! (1)
- June 21 2007 (1)
- June 26 2007 (1)
- June 30 2007 (1)
- Erlang design patterns/best practice? (1)
Recent Comments
- a: :cool: :mad: :twisted: :rol...
- bwb: Very glad to hear that!! Th...
- Guillermo: yes. And what's the problem wi...
- Ciaran: One immediately springs to min...
- Ciaran: For what it's worth, I wrote u...
- Ewan: Love to hear what you find out...
- Ciaran: Very interesting again, thanks...
- Ewan: lol. If there are no decent tr...
- Dan Creswell: And worse it was lost behind a...
- Bert Armijo: There is an alternative to EC2...