4 ms·

What do you mean "networks disconnect" and "hardware fails"? I have no idea what you're talking about.

by onedev 11y ago

erbdex 11y ago
The underlying layers of networking failing- 1. Too many requests for an NIC to handle, 2. Certificates expiring, 3. Firewall changes closing an active port down, 4. A router failing, 5. Congestion, interference in wireless networks resulting in excessive packet loss. Hardware failing- HDDs, RAM, routers crashing, cables at datacenter being accidentally unplugged, racks being misconfigured during upgrades, maintenance etc. See slide #4 here- http://static.googleusercontent.com/media/research.google.com/en//people/jeff/stanford-295-talk.pdf http://static.googleusercontent.com/media/research.google.co...
- onedev 11y ago
  I can just import a 3rd party Javascript library to deal with these right?
  - bsg75 11y ago
    > What are the most annoying things in software development? The idea that everything can and should be done in JavaScript. I know the parent comment was sarcastic, but it reminded me of this trend.
technion 11y ago
I can give you an example. I inherited a system which, on a scheduled basis, completed the following, in order: * Drop a database * Rebuild that database from REST queries The process took under a second and the "downtime" was acceptable. However, if there was ever a short connectivity outage, or the upstream was down, the result of that was that the database was dropped and inaccessible for 24 hours until the next scheduled run. I'd put forward that we build a new database first and then, only if successful, perform a swap. Maybe we could implement a retry. But then came the response I knew I was going to see: "Well if your network's not reliable hire competent network admins that's not my problem". In a sense they were correct, it wasn't their responsibility to ensure the network doesn't ever drop. It was however, their sheer laziness that led to repeated service outages.
- vram22 11y ago
  Nice story. Reminds me: on a project I was on, we created some tests where we manually pulled the network cable out of some PCs (on a client-server LAN app), to check whether the app at least gave a reasonably appropriate error message instead of just hanging. Fun times.

What do you mean "networks disconnect" and "hardware fails"? I have no idea what you're talking about.

by onedev 11y ago

What do you mean "networks disconnect" and "hardware fails"? I have no idea what you're talking about.

The underlying layers of networking failing- 1. Too many requests for an NIC to handle, 2. Certificates expiring, 3. Firewall changes closing an active port down, 4. A router failing, 5. Congestion, interference in wireless networks resulting in excessive packet loss. Hardware failing- HDDs, RAM, routers crashing, cables at datacenter being accidentally unplugged, racks being misconfigured during upgrades, maintenance etc. See slide #4 here- http://static.googleusercontent.com/media/research.google.com/en//people/jeff/stanford-295-talk.pdf http://static.googleusercontent.com/media/research.google.co...

onedev 11y ago
I can just import a 3rd party Javascript library to deal with these right?
- bsg75 11y ago
  > What are the most annoying things in software development? The idea that everything can and should be done in JavaScript. I know the parent comment was sarcastic, but it reminded me of this trend.

technion 11y ago

I can give you an example. I inherited a system which, on a scheduled basis, completed the following, in order: * Drop a database * Rebuild that database from REST queries The process took under a second and the "downtime" was acceptable. However, if there was ever a short connectivity outage, or the upstream was down, the result of that was that the database was dropped and inaccessible for 24 hours until the next scheduled run. I'd put forward that we build a new database first and then, only if successful, perform a swap. Maybe we could implement a retry. But then came the response I knew I was going to see: "Well if your network's not reliable hire competent network admins that's not my problem". In a sense they were correct, it wasn't their responsibility to ensure the network doesn't ever drop. It was however, their sheer laziness that led to repeated service outages.

vram22 11y ago
Nice story. Reminds me: on a project I was on, we created some tests where we manually pulled the network cable out of some PCs (on a client-server LAN app), to check whether the app at least gave a reasonably appropriate error message instead of just hanging. Fun times.