Published in Web Development on Tuesday, June 8th, 2004
Tips for better error handling and contingency design when your mySQL server goes down.
A mere 24 hours after my original post on contingency design and your mySQL server, life served up a case of lemon flavored twisted irony.
I was going to apply the ideas to a clients site when I had a spare moment, but I was too late when the client suddenly calls and asks "what's with the error message on our site? mySQL server can't connect?".
Great, I'm looking really good here (which of course is more important then how they look to potential clients).
Luckily my own advice was fresh in my head, but this time rather than leveraging google to help out, we did three things:
In the end the client was happy, and we were asked to go ahead and plug any such holes that may exist in the site. No problem, after all, anything can be done, for a price!
Some good ideas, Mike
This topic seems to be everybody\'s new darling (at least regarding all the new entries in my Feed Reader ;)) which isn\'t a bad thing, is it?
Thanks Minz, I really like the whole idea. Trouble is, one can get carried away with all of the possibilities.
For example, we have a real-estate site that updates it\'s db every evening. The property listings are spidered and in Google, and so there is potential for surfers to click thru from Google to a listing that no longer exists. What to do?
For now, we simply apologize and refer them to the search tool, however we could do somthing where we run the referring keywords though the site\'s keyword search. This would give the user alternate options right away. A good idea, but will the client see it as worthwhile, and pay for it?
Comments and Feedback