|Text and/or other creative content from this version of Service-oriented architecture types was copied or moved into Service-oriented architecture with this edit. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted so long as the latter page exists. The former page's talk page can be accessed at Talk:Service-oriented architecture types.|
|This article is of interest to the following WikiProjects:|
|This article has been mentioned by a media organization:|
Cite error: There are
<ref> tags on this page without content in them (see the help page).
A Serious Rewrite is Needed
In my opinion, this article is a mess. The intro is completely at odds with the rest of the article, which is rife with POV statements. The intro itself does not take into account the full scope of the article, and is, in my opinion, in itself cruising extremely close to POV. Taken in its entirety, this article more closely resembles an argument than an encyclopedic entry.
SOA is granular - it means different things at different levels of abstraction. It can be applied at a business process level, a user experience level, and a systems design & development level - each with their own definition of the concept, as defined in 'vernacular' terms.
I think the article needs to reflect this, while at the same time providing an entry point for newcomers to the subject without drowning them with the jargon of any one particular level.Gabhala 00:30, 6 October 2007 (UTC)
- I have to agree, this article is a prototype example of a wikipedia article gone mad. My problem was that reading the article simply didn't prove useful. There are a number of reasons for this:
- The content is vague and wandering, as often happens in wiki articles. Many of the paragraphs seem to be "blobs" rather than a sequential series of sentences that crystallize a central point, which is really a paragraph's job.
- The sentence structures of many of the sentences are technically valid but so complicated that they leave the reader to say "Huh? What was that?"
- Many, many sentences have grammatical problems. I was going to start to correct some of the plural conflicts (things like "the man throws a ball, men throw a ball") but I found so many of them that I decided I didn't have that kind of patience tonight.
- This article reminded me of one of those product manuals that is translated from another language into English through a literal, word-for-word translation. Mroesler 04:03, 12 October 2007 (UTC)
- The intro is very poor and seems to reflect one person's POV - SOA *is* primarily a distributed computing paradigm, as the rest of the article reflects. If SOA is used in areas other than computing, some examples (with references) would be helpful. There are enough books and articles out there that virtually every statement in this article could either be backed up by a reference or removed.--Michig 09:22, 19 October 2007 (UTC)
—Preceding unsigned comment added by 126.96.36.199 (talk) 23:58, 14 June 2008 (UTC)
- I revised the first paragraph in an attempt to open the topic up a little to the way SOA is being used today, hoping someone can step into the space and add more current content. As written, the topic addresses an audience that sounds like it might be an IT person who is on the fence about adopting SOA. I would like the topic to also address a young programmer who is well beyond that fence, and is instead playing in a space where SOA concepts apply everywhere in software development today, and where the internet and its services have become truly transparent so that concepts like SOA are almost taken for granted and are just part of the overall mind-share on how to develop software anymore. Does anyone out there agree with my perspective on this? I am hoping so ... but we'll see what ends up happening to my edit tonight. ; )
- Too many people blowing smoke up each others asses here.. trying to be semantically correct. I will rewrite this when I get a moment. What I will say is that someone has made an attempt to share information even if it is misguided. A few clues here.. Stop trying to mix up SOA with web services... SOA has been around a long time now and there are some very elegant implementations and previous incarnations.. So there we go .. it is both a methodology and a technology.. Now. as technologies evolve and develop, we begin to understand the relevance of things like web services (WS) and so on but then also how things like 'semantics' , 'lexicons'and ontologies play into this. I guess the moral of the story is evolution and growth of knowledge and it's application
To fully understand the context of SOA the notion of atomic structure and nested SOA needs to be considered and understood.
This sentence needs some explaining, if it's even accurate: One can consider SOA a continuum, as opposed to distributed computing or modular programming. Huh? Because up to this point, SOA has been described exactly like a form of distributed computing. Is there a reference? Because it makes no sense. —MiguelMunoz (talk) 21:07, 12 May 2011 (UTC)
- Okay, I went through the article's history and found out that, in it's younger days, the sentence read like this: SOA can be seen in a continuum, from older concepts of distributed computing and modular programming, through to current practices of mashups, SaaS, and Cloud Computing (which some see as the offspring of SOA). (Emphasis added.) And yes, it had references. (This comes from the version dated July 1, 2009) Needless to say, this alters the meaning. I put back the original sentence, altered slightly for clarity, complete with the original references. —MiguelMunoz (talk) 23:04, 12 May 2011 (UTC)
Even with the fix, this sentence just seems odd. The word 'continuum' is lazily and inappropriately borrowed from other fields. Look at the link-to article: you'll find definitions of 'continuum' in the fields of physics, math, philosophy, and psychology; none from the history of technology. I think 'progression' may be what's really meant here. Hult041956 (talk) 21:46, 27 October 2011 (UTC)
Relationship to Web service
Does SOA have the same role and duties as the traditional operating system on a single computer?
I see in the paragraph "In a large network of computers SOA has the same role and duties as the traditional operating system on a single computer. Consequently SOA is designed in analogy to traditional multi-tasking operating systems like Windows, Unix, zOS etc." the attempt to make the SOA concept more understandable, however it is misleading: operating system processes are mandatory to run a computer and, as such, they always perform fundamental and centrally supervised operations, while SOA services are not necessarily in the network running. I suggest to suppress the quoted paragraph. Vittorioolivati (talk) 15:38, 3 August 2013 (UTC)
- I agree. The analogy isn't even particularly accurate in my opinion. --HighKing (talk) 14:26, 31 October 2013 (UTC)
A cited article "The Reason SOA Isn’t Delivering Sustainable Software" in "Criticism" section has a broken link, the only version I found on the web is http://soa.xxxxx.com/news/do-not-publishthe-reason-soa where xxxx is dzone, sice dzone.com is blacklisted by wikipedia — Preceding unsigned comment added by 188.8.131.52 (talk) 18:42, 5 December 2013 (UTC)