8 ms·

Cacheing at the edge might help in certain situations but a global reservation and check-in system seems like the kind of thing that needs to be centralized. I

by zrail 4y ago

Cacheing at the edge might help in certain situations but a global reservation and check-in system seems like the kind of thing that needs to be centralized. I think a more workable solution would have been to treat transit for this data center how most other data centers are organized, with multiple independent uplinks that take different routes into the building. A last-resort point-to-point wireless link would probably be wise as well.

deleted 4y ago
[deleted]
ho_schi 4y ago
Most of the IT-Plans focus on mitigating the outage itself (e.g. multiple uplinks, backup server, fallback datacenter). I argue that critical system shall gracefully handling the outage. If a client caches the flight/passenger data (lets say two weeks) you can print list. Grab a pen and keep going. That is enough for some hours and even days. If you're going advanced you can allow to add (right at the gate/counter) one person to more passengers and so on. You can also go all-in and add code which allows merging of external data i.e. allowing headquarters and airport personnel working at same time. Die Fluggäste wurden auch nicht per Strichliste in die bereitstehenden Maschinen gelassen, weil nach Angaben des Personals wichtige Informationen zum Abflug fehlten. If it works that is an appropriate solution. PS: We cannot see circumstances. Maybe a hack, a burning datacenter, war, co-worker going crazy, international sanctions, storm, flooding, whatever. For example Deutsche Bahn itself suffered recently a sabotage, two entirely independent glass fibers get cut off at same time (one in west-germany, one in east-germany).
- ta1243 4y ago
  A large number of flights are booked with less than two weeks notice, and that's before changes which occur hours or even minutes before flights.
  - rtkwe 4y ago
    Not to mention planes are intentionally overbooked (at least here in the US I presume the same tactic exists to a lesser extent in places like Europe with presumably better consumer protections) to ensure they're flying as close to full as possible so you're constantly needing to access the larger booking information to rebook flights for people bumped or to see who's been moved on to your flight. Two weeks is way too long, a day is probably too long to have a fresh passenger manifest.

by zrail 4y ago

deleted 4y ago

[deleted]

ho_schi 4y ago

Most of the IT-Plans focus on mitigating the outage itself (e.g. multiple uplinks, backup server, fallback datacenter). I argue that critical system shall gracefully handling the outage. If a client caches the flight/passenger data (lets say two weeks) you can print list. Grab a pen and keep going. That is enough for some hours and even days. If you're going advanced you can allow to add (right at the gate/counter) one person to more passengers and so on. You can also go all-in and add code which allows merging of external data i.e. allowing headquarters and airport personnel working at same time. Die Fluggäste wurden auch nicht per Strichliste in die bereitstehenden Maschinen gelassen, weil nach Angaben des Personals wichtige Informationen zum Abflug fehlten. If it works that is an appropriate solution. PS: We cannot see circumstances. Maybe a hack, a burning datacenter, war, co-worker going crazy, international sanctions, storm, flooding, whatever. For example Deutsche Bahn itself suffered recently a sabotage, two entirely independent glass fibers get cut off at same time (one in west-germany, one in east-germany).

ta1243 4y ago
A large number of flights are booked with less than two weeks notice, and that's before changes which occur hours or even minutes before flights.
- rtkwe 4y ago
  Not to mention planes are intentionally overbooked (at least here in the US I presume the same tactic exists to a lesser extent in places like Europe with presumably better consumer protections) to ensure they're flying as close to full as possible so you're constantly needing to access the larger booking information to rebook flights for people bumped or to see who's been moved on to your flight. Two weeks is way too long, a day is probably too long to have a fresh passenger manifest.