 |
 |
 |
|
04.07.09 Focus On Architecture To Succeed In The Cloud  By Mike Kavis A small number of bloggers keep reminding the industry of the lessons learned from SOA. We keep reminding people that to succeed in the cloud there must be a focus on architecture. Well it doesn't sound like many people are listening. The same patterns of destruction that caused so many SOA failures are apparent once again as organizations look to the cloud as their next savior. Here are the patterns that I am referring to: •
People arguing semantics • Vendors rebranding everything as the cloud • People taking a technology first approach instead of a business first approach • IT talking to the business in technical terms • Resistance to change • Ignoring organizational change management, thus not addressing the resistance properly I could go on but you get the point. Each of the patterns I mentioned above were issues that made SOA Initiatives very challenging or flat out fail. I have been seeing so much chatter on Twitter about cloud definitions that I have one definition of my own to offer. Cloud Insanity - To repeat the same behaviors that caused SOA to fail and expect a different result. Let's get back to the basics folks. Public clouds are off premise infrastructure in a shared environment. Your stuff is running on computing resources with other people's stuff. Private clouds can be on or off-premise but are not shared. In other words, you know what servers your stuff runs on. There is no need to get more granular than that. There are a variety of "as-a-Service" terms. Just remember that PaaS (Platform as-a-Service) is infrastructure on a proprietary platform which forces you to code in a certain language. Infrastructure as-a-Service is infrastructure that allows you to build your stuff in any language that you choose. Software as-a-Service is exactly that, software that you pay for that runs somewhere else written by somebody else.
 The definitions do not need to be more complicated than that. What we should be focusing on is business drivers, risks and issues, standards, case studies, and other productive conversations that might help somebody actually deploy something in the cloud. The other issue I see is many people are looking at the cloud because of the hype, not because they have business justification. If you are thinking about moving your complex legacy systems to the cloud, you might want to rethink that strategy. Any value that a business may gain from moving old stuff to the cloud will likely not be realized because of the huge costs and complexities of trying to migrate something built for on-premise to off-premise. It is best to deploy new systems or services to the cloud. They can be architected for the cloud and do not require IT to spend tons of money converting things that already work. Instead, IT can add value by spending time on new things and deploying them in a more efficient manner. Continue reading this article. About the Author: Mike Kavis is a veteran Chief Architect with over 23 years of IT experience including distributed computing, SOA, BPM, data warehouse, business intelligence, and enterprise architecture. Read Mike's blog at Enterprise Initiatives. |
||||||||
|
| ||
|
-- ITProNews is an iEntry,
Inc. publication -- iEntry, Inc. 2549 Richmond Rd. Lexington KY, 40509 ©2009 iEntry, Inc. All Rights Reserved Privacy Policy Legal archives | advertising info | news headlines | free newsletters | comments/feedback | submit article |
