Update: It seems BA’s little mishap cost GBP 58 million!

When we were developing Herschel version 12 we did an in-depth investigation of making it a cloud-based application. Our conclusion was a locally hosted version would be faster and allow us to make the most of our “Minority Report” inspired multi-window approach.

One thing we didn’t really appreciate was with a cloud app you’re really putting your (fragile?) eggs all in one, big, shared basket.

Our local tyre and exhaust shack uses a neat cloud-based ordering / stock package. The last time I was there (yet again a victim of our impressive potholes) the whole system was down. I asked the manager if he’d contacted tech support. He wearily replied that it would be a waste of time, as every branch would be on the phone.

The recent British Airways IT disaster seems to be the same problem but on a much larger scale. I was surprised even ba.com was as dead as a dodo (see picture). And as an interesting Economist article points out (3 June 17 issue), this was actually the third major IT failure for BA in the last year.

Yes, we do get the very occasional AOG situation where immediate Herschel support is needed.  But I dread to think what it would be like if all our users crashed, all at the same time!

One thing we have done is sort out a workaround plan if our cloud-based Freshdesk support management system goes AWOL.

Just in case.