Airlines Suffer Worldwide Delays After Global Booking System Fails (bloomberg.com)
rastos1 writes: Airlines worldwide were forced to delay flights Thursday as a global flight-bookings system operated by Amadeus IT Group SA suffered what the company called a "network issue." Major carriers including British Airways, Deutsche Lufthansa AG, Cathay Pacific Airways and Qantas Airways were among those reportedly impacted by the outage. Singapore's Changi airport said via Twitter that a technical issue affecting some operators was delaying the check-in process, with boarding passes having to be issued manually. "Amadeus confirms that, during the morning, we experienced a network issue that caused disruption to some of our systems," the Madrid-based company said in a statement. Technical teams took immediate action to identify the cause of the issue and services are "gradually being restored," it said.
I'm happy the slashdot IT team found new jobs so quickly.
"National Security is the chief cause of national insecurity." - Celine's First Law
Your words are in English, but your post makes no sense.
That would have been 17 Moore's Law generations ago! In human terms, it like looking at the farming methods or weaving techniques or marine navigation procedures or military maneuvers of 1592!
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Thank you for this - with the week I'm having, I needed a good belly laugh...
You don't understand the principal rule of managing software projects (according to the MBA's who manage software projects): if anything takes more than a couple of hours to do, it's not worth doing.
Proud neuron in the Slashdot hivemind since 2002.
Are these airline information systems really all that fragile in this sector? I know we all say that, but I personally don't have a F clue; I'm 100% media driven on this from what I read, consume or read-between-the-lines. I'm hoping someone close to this could chime in or reply...
With any one of us with any moderate amount of IT experience in the trenches and at any level that's support any ops or for-profit system, It's hard to dismiss a generic statement such as network issue. I know management I've worked under in the past at other organizations, private and government, would pre-can some huggable and down-played message like that --- and I totally get it; it's embarrassing on any level for any end-user disruption, but we'll never know why.
With the amount of breaches, DDOS's and what seems like this popular resurrection of using the word 'Hacking' like we are all hoping a Hackers reunion happens with Jonny Lee Miller and Angelina Jolie is just nauseating, but a very true reality anymore with the lack of implementation over security practices.
AWS has had plenty of outages.
Personally I don't think there is any such thing as "technical issue". There are resourcing, risk management, and personnel management issues. I've built systems with the right teams before that could stand anything short of a nuke, and we came in under budget. Honesty and the right people give you results.
they don't have local console and you are not able to use your own ISO to install an OS.
http://diehard.wikia.com/wiki/...
Requiem for the American Dream
Requiem for the American Dream
... but pushing your pet language in every goddam comments section is a perfect way to make people get sick of hearing about it and give it the finger before they've even tried it. Who knows, perhaps thats your intention. Either way, give it a rest you buffoon.
And it doesn't matter what language they're written in , the fragility generally isn't down to a low level language issue such as memory, threading or pointer issues (though obviously those errors happen too), its usually a logic problem in handling edge cases, unexpected code paths and errors correctly. No language is going to save you from broken logic however much their proponents would pretend otherwise.
Every human built system can suffer from technical issues. Saying otherwise is just pretending the problem doesn't exist.
" I've built systems with the right teams before that could stand anything short of a nuke"
You're modest arn't you. Systems always look bullet proof - until they go wrong. I doubt yours are any better or worse than hundreds of others that have been written to be resilient.
Yes, let's replace a worldwide booking system that for the most part handles 3.7billion passengers every year without issue because of a very occasional outage causing a few queues.
What could possibly go wrong.
I've built databases that work flawlessly for a year and stop working when I'm on vacation without explanation. Shit happens sometimes.
"Action without philosophy is a lethal weapon; philosophy without action is worthless."
...until the manager's flight is canceled, and [s]he is standing in an airport full of people in the same situation, including FAA regulators and Rand Paul.
Then there might be sufficient motivation to refactor.
...is mostly syntax-equivalent with Oracle PL/SQL. The GCC toolchain targets ADA with GNAT. As such, it would obviously link against C.
ADA is quite old and is likely missing many of the features you've outlined. Some of them may be present in the popular descendant of ADA known as SPARK.
It is well-known that our software breaks far too much. Denying the problem does not solve it. ADA was designed to address this issue head-on, which is why Boeing's airplane control software is not written in C.
You're attributing much longer memories to them than they seem to have. A co-worker and I were talking about refactoring and tech debt (and why we had so much still floating around) and he made an observation that (to management) tech debt is like a leaky roof. You don't have to fix it when it's not raining.
Proud neuron in the Slashdot hivemind since 2002.
From a person who has had similar international headlines for systems that I can impact. My heart goes out to you. System failures are never fun, failures that affect a lot of customers are just plain stressful. Document processes and learn from this event all the you can. Customers care most what was learned and how to prevent this and future scoped events from occurring again.
Hang in there!
There is or can be built a machine that can simulate any physical object. -Church-Turing principle
Reportedly it was due to equipment failure
If you trust some with the name "Logan, A Bot"...
Ezekiel 23:20
Who the fuck is creimer??
Isn't that the guy living next door to Alice?
Ezekiel 23:20
He's using the wrong words, but essentially he's saying that they get to charge you for their mistakes caused by having lousy IT that is lousy because they are saving money by not spending it on training.
Nah. It must be rewritten in Javascript. With Angular.js, Node.js, and a whole load of other *.js's or it won't Web Scale!