Planning for failure

I spent twelve years composing music (“tracking”) for Trideja, and having officially retired sometime in … 2001, I’ve stayed in contact with those still active in the scene and even contribute here and there when time allows. Tracking is a time consuming process, moreso than picking up any instrument, though that’s not the measure of its value.

So noticing that the site has gone down, I wonder why there isn’t a better backup system for websites. Is it so difficult to maintain a redirect for the event of such? It would have to happen in the backend, server level, but doesn’t buy celebrex that sound logical?

Say for example eBay is down, but you still need to manage your billing to ensure things are paid and shipments occur in time. Why not have a secondary system for this that kicks in should the primary be unavailable?

Is it too much to ask to do this? Technically complex? I doubt it, websites are already a hodge-podge of asynchronous code and media. Perhaps HTML5 will better facilitate this in the future, but even a brief search indicates there’s no priority given to backups, or support systems of this nature.

And why not? It’s an interesting question.

  • January 22, 2016