Distributed Data & Software - blah, blah, blah

For the last thirty years systems people have been concerned with the integrity of data. How to ensure that once we have captured something we do not allow it to be corrupted, inadvertently deleted, etc. So how do you achieve the same objective when the data is spread around, when the users are spread around, when the software is made up from disparate elements, and when it is difficult to see the wood for the twigs for the branches for the trees for the woods for the forests for continents for the Earth for the Universe. OK, I exaggerate, so shoot me.

Then there's the question of controlling the correct versions of software. Making sure that the correct versions are in use in all devices at all times. New releases of software being a especially entertaining but again, if you are just building the software then somebody else can handle this can't they? As you move through development and production running you not only need to know what the current configuration is but what it was at a certain time and any planned future changes.

Now you did not believe that you get away forever from any responsibility did you? I am afraid that designing and building the recovery into the system has to be your responsibility. But do not worry, I am absolutely sure that all the components will fit together perfectly and deliver you transaction level recovery just the way you used to know it.

Ideally, the user should only be required to sign onto the system once, no matter how many layers or levels are between him and the data and applications he wants to get to.

We are nearly there, that was not so bad was it? Only one more hurdle to go. All we have to do now is to test this system! Oh, my god!