4 ms·

We do guarantee an SLA and use precisely nothing other than sysv init. We pick software that is reliable and trustworthy then test it thoroughly. Those are fo

We do guarantee an SLA and use precisely nothing other than sysv init. We pick software that is reliable and trustworthy then test it thoroughly. Those are forgotten arts outside of the enterprise. Elsewhere, any new technology that falls from the sky is picked whether it works properly or not.

buster 13y ago
How do you cope with hardware failure, corrupt memory banks, temporary network failures, you also just buy "hardware that never fails"? Just testing something and deeming it reliable enough to "just run" is a horrible practice. There is no software on earth that is bug-free, you do realize that, yes? Why do you think the NASA builds rockets with many many safety measures? Because they use the latest and greatest hardware and software? Or because they KNOW that at some point something WILL fail. It's not a only a question of picking stable software. The skill is to be prepared for the emergency at any time, even if it is on a rare occasion. If your only safety measure is to "just pick stable stuff", i'd surely never buy your service.
- harrytuttle 13y ago
  Firstly, calm down. I gave you a small peek into my world and you're drawing a lot of bad assumptions from it. We mitigate hardware issues with either hot spares or clustering. We have three datacentres distributed geographically with entire redundant sets of equipment (4x 42U racks in each). With respect to software failures, we test everything thoroughly including failover conditions etc. Everything is load tested as well. We are prepared for emergency. We have dedicated people ready to jump on that. However preventing these things ever being needed is a professional responsibility which is my point.
  - deleted 13y ago
    [deleted]
- asdasf 13y ago
  The poll is about the fad of using a program to monitor your known to crash/leak/whatever app, generally starting it, monitoring it, and restarting it. Hardware failure is completely irrelevant to the discussion.

buster 13y ago

How do you cope with hardware failure, corrupt memory banks, temporary network failures, you also just buy "hardware that never fails"? Just testing something and deeming it reliable enough to "just run" is a horrible practice. There is no software on earth that is bug-free, you do realize that, yes? Why do you think the NASA builds rockets with many many safety measures? Because they use the latest and greatest hardware and software? Or because they KNOW that at some point something WILL fail. It's not a only a question of picking stable software. The skill is to be prepared for the emergency at any time, even if it is on a rare occasion. If your only safety measure is to "just pick stable stuff", i'd surely never buy your service.

harrytuttle 13y ago
Firstly, calm down. I gave you a small peek into my world and you're drawing a lot of bad assumptions from it. We mitigate hardware issues with either hot spares or clustering. We have three datacentres distributed geographically with entire redundant sets of equipment (4x 42U racks in each). With respect to software failures, we test everything thoroughly including failover conditions etc. Everything is load tested as well. We are prepared for emergency. We have dedicated people ready to jump on that. However preventing these things ever being needed is a professional responsibility which is my point.
- deleted 13y ago
  [deleted]
asdasf 13y ago
The poll is about the fad of using a program to monitor your known to crash/leak/whatever app, generally starting it, monitoring it, and restarting it. Hardware failure is completely irrelevant to the discussion.