Commentary

Alice LaPlante
 

Education Key To SOA Success

We have the results of two surveys from SOA Pipeline for you this week. The first one asked, why consider implementing an SOA? Not surprisingly, more than half of you (53 percent) said you were seeking to lower integration costs. After all, analysts report that the majority of IT budgets these days are going toward integration efforts, and an SOA does promise to enable easier connections between applications and data.
We have the results of two surveys from SOA Pipeline for you this week. The first one asked, why consider implementing an SOA? Not surprisingly, more than half of you (53 percent) said you were seeking to lower integration costs. After all, analysts report that the majority of IT budgets these days are going toward integration efforts, and an SOA does promise to enable easier connections between applications and data.Another 30 percent said that the main reason for implementing an SOA was to get the ability to reuse services; finally, 17 percent said they were doing so to give them faster project turnaround.

Our second survey inquired about the chief challenges of implementing an SOA. This one had a surprise in it: the No. 1 roadblock, according to 56 percent of you, was the need to educate people about SOA. Other recent surveys have said that concern about proliferating standards was the chief stumbling block to SOA nirvana, but in this particular one only 12 percent agreed with that statement. A full 20 percent were concerned about their ability to reuse standards; 8 percent cited worries about security; and 4 percent said they were concerned about the lack of internal processes.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links