Many people in the industry are debating whether cloud computing will replace or supplant service oriented architecture. Dave Linthicum says this is not the case, as SOA and cloud are part of the same package. The key to success, he says, is to stay focused on enterprise architecture.
Dave, a noted industry consultant and ebizQ community leader, shared his views on the SOA-to-cloud paradigm at recent ebizQ Webcast, joined by Ed Horst, VP of product strategy for AmberPoint, and moderated by yours truly.
Cloud computing is made possible by SOA, Dave argues. "SOA and cloud computing are related one to the other," he relates. "Service oriented architecture is all about sharing services and sharing information, processes, and agility integration and governance. And cloud computing is all about providing architectural options, such as software as a service, database on service, and platform on demand."
In both cases, the name of the game is agility, he explains. "The value proposition of service oriented architecture versus traditional architectural approaches is the ability to take advantage of agility. Since we address everything as services, we're able to configure and reconfigure those services, either in composite applications, such as mashups, or binding them into processes, or abstracting them into applications."
Ed Horst discussed in detail the issues around transaction management across clouds, and pointed out there common elements required for transaction management -- including timeliness, the ability to diagnose problems in individual transactions, performance, and security requirements.
Not all services are suited for the cloud, Dave says. The "loosely coupled" aspect of SOA is an important ingredient for cloud implementations as well. The best scenarios for moving services to the cloud is "typically when applications and processes and data are more loosely coupled and less dependent on each other," he states.
Cloud computing provides new architectural options in the way services are deployed, Dave relates. "So instead of just looking at complete on-premise solutions, where we were binding and placing systems and services just within our data centers, we have architectural options such as Amazon and 3tera."
Cloud formations require the same enterprise architecture and governance -- encompassing technology, people, and processes -- that companies are now putting into place to manage SOA. "To make sure you're leveraging cloud computing properly in the context of your architecture you need to have a governance strategy," Dave relates. "You need to manage those services within a context of a larger enterprise. This is probably one of the most important aspects of service oriented architecture and one of the most important aspects of cloud computing as well. Because if you do not have a strong governance approach and governance strategy, then you're not going to be successful."
Dave's book on SOA and cloud, Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide, is now available on Amazon, and will be released in print in October.
Dave, a noted industry consultant and ebizQ community leader, shared his views on the SOA-to-cloud paradigm at recent ebizQ Webcast, joined by Ed Horst, VP of product strategy for AmberPoint, and moderated by yours truly.
Cloud computing is made possible by SOA, Dave argues. "SOA and cloud computing are related one to the other," he relates. "Service oriented architecture is all about sharing services and sharing information, processes, and agility integration and governance. And cloud computing is all about providing architectural options, such as software as a service, database on service, and platform on demand."
In both cases, the name of the game is agility, he explains. "The value proposition of service oriented architecture versus traditional architectural approaches is the ability to take advantage of agility. Since we address everything as services, we're able to configure and reconfigure those services, either in composite applications, such as mashups, or binding them into processes, or abstracting them into applications."
Ed Horst discussed in detail the issues around transaction management across clouds, and pointed out there common elements required for transaction management -- including timeliness, the ability to diagnose problems in individual transactions, performance, and security requirements.
Not all services are suited for the cloud, Dave says. The "loosely coupled" aspect of SOA is an important ingredient for cloud implementations as well. The best scenarios for moving services to the cloud is "typically when applications and processes and data are more loosely coupled and less dependent on each other," he states.
Cloud computing provides new architectural options in the way services are deployed, Dave relates. "So instead of just looking at complete on-premise solutions, where we were binding and placing systems and services just within our data centers, we have architectural options such as Amazon and 3tera."
Cloud formations require the same enterprise architecture and governance -- encompassing technology, people, and processes -- that companies are now putting into place to manage SOA. "To make sure you're leveraging cloud computing properly in the context of your architecture you need to have a governance strategy," Dave relates. "You need to manage those services within a context of a larger enterprise. This is probably one of the most important aspects of service oriented architecture and one of the most important aspects of cloud computing as well. Because if you do not have a strong governance approach and governance strategy, then you're not going to be successful."
Dave's book on SOA and cloud, Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide, is now available on Amazon, and will be released in print in October.
Leave a comment