Caution, it’s SOA humor day.
With all the talk of institutions being ‘too big to fail’ and bailouts and such, I can’t help but stop and ask ‘is SOA too big to fail’?
Has the United SOAs of America named a TSAR (to run the Toxic SOA Asset Relief) program? (OK I should have used that on April 1 but the competition is too tough that day).
Is the medicine for Toxic SOA the cure-all magical ‘private cloud’? You’d think so if you’d had some of the conversations I’ve had lately with IT and vendors.
Yes, the concept of private cloud is valid, but as with many terms, overused, overhyped, and misapplied. The private cloud fixation is not just for data center people trying to claim that their ‘well run data center’ is now a cloud (poof), but also for SOAphiles claiming that what they’ve been doing (or in the case of vendors, selling) is now a private cloud. What’s that thundering sound we are hearing across the IT landscape? It’s all the SOA hangers-on jettisoning the former sacred cow and jumping onto the ‘private cloud’ bandwagon.
This type of ‘cloudwashing’ is inevitable. But, what really matters is that we don’t just blindly allow it to kid ourselves into simply relabeling something that hasn’t worked into something else that will also likely not work. I can already see the Ann Thomas Manes post of 2012 declaring that private clouds are dead…
My use of the term SOA is that of the common use (e.g., enterprise class use of SOA concepts, typically top-down big projects), not the official Gartner use which is broader and includes concepts like WOA.
Also, of course, restating and emphasizing that the opinions in this piece are mine (and those of like-minded SOAphobes) and not official research positions of Gartner.
And if you don’t like SOA humor, then why are you reading my blog?
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.