4 ms·

> Note that what I meant by that isn't that your services aren't expected to be up for a month. It's that redundancy is expected (2+ instances behind a load bal

> Note that what I meant by that isn't that your services aren't expected to be up for a month. It's that redundancy is expected (2+ instances behind a load balancer) so servers are resilient to failure. I guess thats why he mentioned gameservers specifically, as those often depend on being a single node

int0x80 8y ago
Even if not a gameserver, virtually anything should not be buggy after one month of uptime. That is just ridiculous. Redundancy is completely orthogonal to this issue.
- baybal2 8y ago
  I hate and like people behind JS development as a language at the same time. Node.js devs more than anybody else realize what's wrong with the general direction of mainstream webdev languages, while at the same time cultivating that culture around themselves like that. A good decision they made was not using high level IO abstractions that both eats performance, and obscures synchronicity implications. And the bad one is their general chabuduo attitude. While nobody in a sane mind will use node.js for an airplane autopilot,or a space mission software, there is no reason for them not to strive for improving node.js reliability to the extend demanded in the "serious software" industry
  - mintplant 8y ago
    > While nobody in a sane mind will use node.js for an airplane autopilot,or a space mission software, The Nightscout artificial pancreas system runs Node.js. https://github.com/nightscout/share2nightscout-bridge/blob/master/index.js#L353 https://github.com/nightscout/share2nightscout-bridge/blob/m... With this bug, glucose monitor readings would stop being delivered after 25 days.
sp332 8y ago
And if you boot all your redundant servers at the same time, they're all going to go down pretty close to the same time as well.
- pvorb 8y ago
  And you also need to know about this bug in order to make your server go down after 2^31 ms. As stated in the Github issue, the service remained otherwise functional.
  - NullPrefix 8y ago
    So the lesson learned: Dont' check if the service is up, just restart it anyways.
- int0x80 8y ago
  Exactly, that is one of the problems.

int0x80 8y ago

Even if not a gameserver, virtually anything should not be buggy after one month of uptime. That is just ridiculous. Redundancy is completely orthogonal to this issue.

baybal2 8y ago
I hate and like people behind JS development as a language at the same time. Node.js devs more than anybody else realize what's wrong with the general direction of mainstream webdev languages, while at the same time cultivating that culture around themselves like that. A good decision they made was not using high level IO abstractions that both eats performance, and obscures synchronicity implications. And the bad one is their general chabuduo attitude. While nobody in a sane mind will use node.js for an airplane autopilot,or a space mission software, there is no reason for them not to strive for improving node.js reliability to the extend demanded in the "serious software" industry
- mintplant 8y ago
  > While nobody in a sane mind will use node.js for an airplane autopilot,or a space mission software, The Nightscout artificial pancreas system runs Node.js. https://github.com/nightscout/share2nightscout-bridge/blob/master/index.js#L353 https://github.com/nightscout/share2nightscout-bridge/blob/m... With this bug, glucose monitor readings would stop being delivered after 25 days.

sp332 8y ago

And if you boot all your redundant servers at the same time, they're all going to go down pretty close to the same time as well.

pvorb 8y ago
And you also need to know about this bug in order to make your server go down after 2^31 ms. As stated in the Github issue, the service remained otherwise functional.
- NullPrefix 8y ago
  So the lesson learned: Dont' check if the service is up, just restart it anyways.
int0x80 8y ago
Exactly, that is one of the problems.