Maybe you have observed how magical the net is?

I am talking about, sure, it’s technology, not magic. But it is nearly as if Web-enabling something provides it with a brand new existence, a brand new depth that simply makes applications more dynamic, more enjoyable, more…magic.

Maybe this is exactly why WOA – Web-oriented architecture – is generating this type of buzz, despite the fact that, at its technological heart, it’s essentially Web-enabling SOA.

WOA = SOA REST World wide web

Gall first created the word in 2005, so in ways, he’s titled to define it – although, to become fair, Dion Hinchcliffe has contributed substantially towards the effort.

After I spoken with Gall, he pointed out Gartner ran an investigation note about WOA. It printed now underneath the title, ” Tutorial: Web-Oriented Architecture: Putting the net In Web Services.”

If you are moving your vision, you are most likely not by yourself. The report’s co-author, Anthony Bradley, even blogged concerning the report underneath the insightful, if somewhat sarcastic, title, ” I Simply Learned SOA and today I must Learn WOA”?”

I can tell how some would think WOA is really a covering game. Gartner defines “Web-oriented architecture” as sub-type of service-oriented architecture, in line with the Web. Just like it’s SOA sire, WOA is affected with many of the same problems: An imprecise definition, vague statements about “architectural style” rather of specifications or standards, and couple of actual real life deployments. Some express it really just boils lower to selecting REST over SOAP.

Dion Hinchcliffe published a really thorough explanation from the functional distinction between SOA and WOA captured. What I’ve not seen is a straightforward, straightforward and short undertake why companies should worry about WOA, particularly because of the disillusionment with SOA.

It appears as though this can be among the issues the Gartner report attempts to pin lower, since report’s summary includes this:

“WOA’s goal would be to transform traditional application-to-application integration from the ‘rat’s nest’ of specialised interfaces right into a generic web of globally linked hypermedia.”

That’s concerning the best explanation I have seen on why companies should worry about WOA. To simplify even more, I’d offer this summary, obtained from my readings and interviews on WOA:

WOA provides the same advantages of SOA, plus all of the pros from the Internet -URI-identified endpoints, HTTPS and, possibly most significantly, mashup abilities.

You’ll find that what’s missing from that summary would be the downsides of WOA. I’m definitely not attempting to pretend there’s not downsides – although at this time, the disadvantages are pretty fuzzy. I am just trying to provide you with a concept of the company situation for WOA and why it’s attracting everyone’s attention at this time.