As we build ever larger storage estates and generate ever increasing amounts of data; I realised yesterday that a project that I am currently involved planning of the implementation has no migration path out of. The decision that we have made is pretty much final, this is it; once this ball starts rolling, it doesn't stop and once it's built; it'll take the rest of my career to migrate out of.
And boy is that a scarey thought; this is a bet your house moment! I'm wondering how may people are actually heading down that route, making decisions which are going to have to be lived with for a lifetime.
I think that we've spent 40-50 years building open-sewers and I think we are going to spend the next 5 years building a sewer-system which will stand the test of time and will have to because digging them all up again is just going to be too hard.
Hmm. Putting in something that will be hideously hard to migrate away from. You’ve bought Centera have you? đŸ˜‰
Gods no!! The thought of that sends shivers down my spine!
Sounds truly scary – in every good design there should be a get out of jail free option – rather you than me!
Hmmm…another guess: embedded UNC names in a database? No, I know you wouldn’t do that. But I am really curious about this project. What’s the implementation like if it’s impossible to migrate out of?