IT Best Practices

Adopt the cloud, kill your IT career

Paul Venezia's title for this article may be a touch concerning, but his point is valid: if you decide to move a troubled component to a cloud vendor, you're simply adding more complexity to something that is already a headache. By bringing in another “set of hands” you're effectively creating another possible point of failure: It's not just the possibility of empty promises and integration issues that dog the cloud decision; it's also the upgrade to the new devil, the one you don't know. You might be eager to relinquish responsibility of a cranky infrastructure component and push the headaches to a cloud vendor, but in reality you aren't doing that at all. Instead, you're adding another avenue for the blame to follow. The end result of a catastrophic failure or data loss event is exactly the same whether you own the service or contract it out. The difference is you can't do anything about it directly. You jump out of the plane and hope that whoever packed your parachute knew what he or she was doing. To push past this risk and move towards a faster, stronger IT organization who utilizes a cloud vendor, Venezia suggests always verifying what the vendor is doing, keeping what you can still control under your control, and making sure you have backup plans outside of what the vendor supplies.

Show More

Leave a Reply

X

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.