Commentary

Chris Murphy
Editor, InformationWeek  

A Better Way Than SOA?

Here in the summer of $4-a-gallon gas, it's serious business to liken something to a honkin' SUV. Yet that's how we portray service-oriented architectures in the illustration on the cover of InformationWeek magazine this week. We're raising the question about development methods that people are asking about SUVs: Do I need, and can I afford, all that horsepower?

Here in the summer of $4-a-gallon gas, it's serious business to liken something to a honkin' SUV. Yet that's how we portray service-oriented architectures in the illustration on the cover of InformationWeek magazine this week. We're raising the question about development methods that people are asking about SUVs: Do I need, and can I afford, all that horsepower?In his article, Roger Smith makes the case for Web-oriented architectures as a simpler alternative to SOA, one that's too often overlooked. Smith notes the appeal of SOA to businesses, but also the simmering dissatisfaction. About a third say SOAs fell short of expectations in our research, and almost 60% say it increased complexity. Just 10% say it exceeded expectations. Writes Smith:

The lesson is that more often than not, simpler is better. A growing number of companies are finding that lower-visibility Web-oriented architecture (WOA) developments, spawned through grassroots movements, are a better route to the service-oriented architecture.

More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The risk and complexity that comes with an SOA are a bit like getting 13 miles to the gallon. It makes perfect sense -- if it's the only way to get the job done right. But for a possible alternative, give Smith's article a read. And please share your own experiences with us.

(Click here to see our SOA-as-SUV cover art, and here for PDFs of any InformationWeek magazine issue. Free registration required for the PDFs.)


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