Comments on: Cloud Insanity – Focusing on all the wrong things, again http://www.kavistechnology.com/blog/?p=890 Three Keys to a Winning IT Department - Technology, Business, and People Tue, 31 Aug 2010 22:15:09 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: The real problem with Cloud Computing….People http://www.kavistechnology.com/blog/?p=890&cpage=1#comment-618 The real problem with Cloud Computing….People Thu, 07 May 2009 03:05:08 +0000 http://www.kavistechnology.com/blog/?p=890#comment-618 [...] of SOA. Now we have simply changed the marketing slides from SOA to Cloud Computing and the same pattern of insanity commences. Cloud Insanity - To repeat the same behaviors that caused SOA to fail and expect a [...] [...] of SOA. Now we have simply changed the marketing slides from SOA to Cloud Computing and the same pattern of insanity commences. Cloud Insanity – To repeat the same behaviors that caused SOA to fail and expect a [...]

]]> By: MikeKavis http://www.kavistechnology.com/blog/?p=890&cpage=1#comment-556 MikeKavis Wed, 22 Apr 2009 17:47:47 +0000 http://www.kavistechnology.com/blog/?p=890#comment-556 @Dave Exactly. I am glad I am not alone with these thoughts! @Dave

Exactly. I am glad I am not alone with these thoughts!

]]> By: Dave Pickens http://www.kavistechnology.com/blog/?p=890&cpage=1#comment-555 Dave Pickens Wed, 22 Apr 2009 17:42:41 +0000 http://www.kavistechnology.com/blog/?p=890#comment-555 I think the issue pretty much comes down to organizations doing "science experiments" rather than architecture when it comes to doing these things. There's no specific governance driving the behavior so the technology is being miss applied -- under applied (risk adverse) or over applied (hammer looking for a nail) or mal-applied (round peg in a square hole). Like you said, get back to basics of business drivers and architecture -- quite frankly it doesn't matter whether it's on premise or off... a service or not... what matters is "Why's" and "What's" and "How's"... Why this path vs. that path? Under What conditions is it acceptable to do this vs. that? How is it going to measured in terms of success? And then not play favorites... if the architecture principles say that X requires a specific level or type of security and that generally Q sort of service level, then you shouldn't dismiss doing it on the "cloud" or as an outside service if it meets the requirements... too many times I see the implement first because it's "cool" and then back into the requirements later... Let's start with the business drivers and requirements first. {sigh} I think the issue pretty much comes down to organizations doing “science experiments” rather than architecture when it comes to doing these things. There’s no specific governance driving the behavior so the technology is being miss applied — under applied (risk adverse) or over applied (hammer looking for a nail) or mal-applied (round peg in a square hole).

Like you said, get back to basics of business drivers and architecture — quite frankly it doesn’t matter whether it’s on premise or off… a service or not… what matters is “Why’s” and “What’s” and “How’s”…

Why this path vs. that path? Under What conditions is it acceptable to do this vs. that? How is it going to measured in terms of success?

And then not play favorites… if the architecture principles say that X requires a specific level or type of security and that generally Q sort of service level, then you shouldn’t dismiss doing it on the “cloud” or as an outside service if it meets the requirements… too many times I see the implement first because it’s “cool” and then back into the requirements later…

Let’s start with the business drivers and requirements first. {sigh}

]]> By: Jason English http://www.kavistechnology.com/blog/?p=890&cpage=1#comment-497 Jason English Tue, 07 Apr 2009 05:46:03 +0000 http://www.kavistechnology.com/blog/?p=890#comment-497 You are really onto something Mike - we'll see where this goes next. I have always been of the mind that the future of the cloud is the past of SOA and Virtualization for that matter - one of proliferating a bunch of services, or VMs, or cloud-based services/software/environments for short-term gain. It is easy to start, and then it becomes evident that some real architectural thought, validation and mitigation of unexpected issues and use-based cost has to take place if we are going to trust it for enterprise use. SOA overcame a generation of half-baked services and is now working responsibly for companies, no matter what they call it. The same will apply to services thrown into the cloud without an architectural plan and business justification. Hopefully this time we'll be able to keep perspective. You are really onto something Mike – we’ll see where this goes next. I have always been of the mind that the future of the cloud is the past of SOA and Virtualization for that matter – one of proliferating a bunch of services, or VMs, or cloud-based services/software/environments for short-term gain.

It is easy to start, and then it becomes evident that some real architectural thought, validation and mitigation of unexpected issues and use-based cost has to take place if we are going to trust it for enterprise use. SOA overcame a generation of half-baked services and is now working responsibly for companies, no matter what they call it.

The same will apply to services thrown into the cloud without an architectural plan and business justification. Hopefully this time we’ll be able to keep perspective.

]]>