Some relationships seem to reflect the natural order of things. Examples that come to mind include night giving way to day, rain and thunder, winter turning to spring and (at least in the Deutsche household when our boys were younger), peanut butter and jelly.
It seems to me this same type of relationship exists between a cloud architecture and a services-oriented enterprise (SOE is comprised of a services-based infrastructure, services-oriented architecture, and services-oriented enterprise management). In my latest industry perspective on Data Center Knowledge, I discuss my fourth fundamental truth of cloud computing strategy: services-oriented taxonomy is not optional.
As in earlier posts, I use an example from the automotive vertical to demonstrate why SOE is a necessity if youâ€™re looking to build a robust cloud architecture. To this end, I use Henry Fordâ€™s Model T to draw a parallel between assembly line standardization and interchangeable parts to the need for a cloud-based application to integrate back into a companyâ€™s application portfolio. Paralleling the experience of the Ford Model T production lines, whether and how this is done drives both assembly and lifecycle costs of the entire cloud effort.
At the moment, I simply donâ€™t see a clear path for the cloud to fully deliver its potential without some kind of services-based architecture running on the back end of the enterprise. As always, I hope you can share your companyâ€™s real-world experience of moving to the cloud to either support or contradict my conclusion.