Part of service oriented architecture is document oriented architecture. Not really, but people in this industry tend to think that way since that is how web services work and they are very confused.
Other than that, the rest of your argument is logical and very well done but:
I don't think that there is any value in trying to define a vacuous term like SOA. If its originators had intended to provide a useful solution instead of a buzz word on which they could sell products they would not have intentionally left its definition so vague and ambiguous.
Trying to define SOA as something useful in the real world, rather than coming up with something useful in the real world and giving it a name is confused pedagogy and exactly the opposite of what we should be doing. Coming up with a model that fits the real world is science. Trying to make the real world fit the imaginary model is religion.
Like every cult before it the SOA cult is going to fall flat on its face because it is comprised of a bunch of wackos who have abandonded reality. |
java.net RSS Feeds
