--- In [email protected], Michael Poulin <m3pou...@...> wrote: > > Rob, what makes an application a service? IMHO, it is the > application behaviour, not its interface. In my example, I have > created a service on the top of Documentum (it was not an interface > Documentum did not give us its code).
IMO, what you described was an interface to Documentum, not a "service on top." Who authored the code is immaterial. The activity/characteristics you described pertained to the interface. The Documentum behavior (RWE) did not change. What changed is how messages get to it. > The service used Documentum publishing engine as the data resource > and operated triggered by the publishing events. [Thanks for > reminding me that the 'interface does not make service out the > application', I pleased you attribute it to m :-) ] To be clear, I don't think I credit you with coming up with that--just that it is an aspect you've pointed out many times in the past. > > Generally, don't you think that a pub/sub (vs. P2P) as well as an > orchestration (vs. choreography) are natural SO solutions/patterns? I don't think any particular interaction style is "more SO" than any other. Pub/sub and P2P interactions are fine. Orchestration vs. choreography both fit in an SO environment. -Rob
