Michael Poulin wrote: > To my understanding, you can link/integrate even technical components in > certain style that makes 'integrated' entities to be capable of serving > in accordance to the SO principles. The resulting entities are SOA > services not because of used integration but because > of SO principles preserved during the design and implementation. This is > why I against the motto: "SOA is integration"
Integration between people has typically been, at what point can we make something that we can hand off to Joe so that I can do something else in parallel with what Joe is doing, or how can I not be responsible for the work item X by making sure I can give it to Joe to do. Either I have to train Joe (integrate my knowledge of the payload with his work flow), or I have to learn what Joe knows how to do, and reshape my needs around the task that he can already do. In terms of paper and pen, I like to say the pen is like the invocation layer. If I want to convey something, I have to be able to indicate my intent. The ink in the pen is the marshalling layer. It's how I represent my intentions. The paper I would write on is the transport layer. It's how my request gets transported to Joe. Back to the people parallel, Joe might be willing to provide me paper, but generally, I can use lots of different types of paper as long as my ink works on that paper. The more I depend on Joe to provide the paper, the ink and the pen, the less I have to know to integrate with Joe. If I have to provide all three items, then Joe has to be able to understand all three. Many types of technologies codify all three by making it necessary for both ends to agree on all three aspects, at some level. It's just not beneficial to have to guess about what you have. If Joe can recognize what I've written, then he can do what I need him to do. If, he has to type it into google translations because I wrote it in spanish, and he only knows latin, then we can have a loss of specificity in that translation. This is where marginal marshalling technologies break down in integration. The less you have to assume or guess about, the more rigorous you can assume the interchange to be. The more specific you are about the technologies, the less you have to guess about and assume. Gregg Wonderly
