My keynote at the Microsoft SOA and BP conference has generated a bit of press, including this excellent summary by Darryl Taft ("Gartner: How to Unify Your SOA Roll-Out") and this take on a quote from that article by Joe McKendrick ("Analyst: ‘you’ll all be doing SOA in 18 months whether you plan to or not’"). While both articles are accurate overall, I wanted to put the "18 months" comment in context. So I left the following comment on Joe’s post:
Joe, While I am bullish on the concepts that constitute SOA (modularity, distributability, discoverability, sharability, loose coupling), I am less bullish on the name "SOA" given how it has wound up meaning just about anything anyone wants it to mean.
As for the "18 month" comment, I was using "SOA" somewhat tongue-in-cheek. What I was referring to was the SEC announcement in 2008 that between now and 2011 it will be phasing in mandatory use of XBRL for financial reporting into the SEC.
Since the audience was primarily composed of IT employees of public companies regulated by the SEC, I thought I would highlight that "everyone" will have to use the automated SEC reporting service to deliver their 10Qs etc. in the form of XBRL. This is what I meant by "you’ll all be doing SOA in 18 months or so".
But of course, one isn’t really "doing SOA" unless the system one creates using services is modular, distributable, discoverable, sharable, and loosely coupled — something I pointed out later in the talk.
Feel free to add your 2 cents either here or on Joe’s post.
Read Complimentary Relevant Research
Four Ways for CIOs to Cultivate Digital Dexterity in Leadership and the Workforce
To thrive in the digital era, enterprises need digital dexterity as an organizationwide competency. CIOs can boost their value by developing...
View Relevant Webinars
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.