The Windows Azure APIs came a long way since they were originally released. On a few occasions, the new versions weren’t very backwards compatible. During those moments, people who use the APIs directly in their code had a tough decision to make.
Do we rewrite the code or stay with older APIs?
That’s a tough place to be! This is why my message is so important, don’t be a fool, wrap your tool!
Creating adapters or facades for external dependencies is practice that should be a natural reflex.
There are times when it can be difficult to fully isolate dependencies, because its not always as simple as it sounds. When this situation comes up, design patterns can be used to guide and inspire our work. Keeping the bits of code that you do not control isolated will save your company a lot of money. Every time a new update comes out, which by the way is almost every 3 to 4 months, your company is going to ask itself the same question.
Do we take the risk of updating?