You're right. I was incorrectly overlooking the RWE/behavior that exists behind the interfaces. Definitely important at the architecture level. Thanks for the gentle correction.
Regarding bullet 5, we agree that SOA and EDA principles mesh together nicely when defining a given architecture. The principles of either notion can exist with or without the other. EDA is not a subtype of SOA, nor vice versa. Nor do I think that EDA is an implementation approach. EDA != pub/sub. -Rob --- In [email protected], Michael Poulin <[EMAIL PROTECTED]> wrote: > > Looks like we are getting into discussion of what is SOA again... Here are my -----1: > > 1) The focus of SO is primarily on ... services! Interfaces is only communication mechanisms serving the purposes of services IF programmers do not see further than interfaces, it does not mean there is nothing. Other IT roles can and have to see behind the interfaces > > 2) For all intents and purposes of PROGRAMMERS, the interfaces are the services. All CONSUMERS are interested in business functionality and Real World Effects provided by the service body > > 3) SOA and, especially, SO is not about HOW but about WHAT, WHY and WHO. Consumers do not care how a service, i.e. service body, is implemented, they only care about WHAT the service does and have to decide WHY they need this service. > > 4) from an SO perspective, there is not much more to a service INVOCATION than its interface. When you bring your favorite <SPAN id="misspell-2" class="mark" >AWM</SPAN> 3-3.<SPAN id="misspell-3" class="mark" >indd</SPAN>Hawaiianshirtto the laundry, you do not care if there is a regular or revolving door in the shop, you only care whether the laundry uses bleach or color-saving stuff, how they do washing - it does not matter. The business function in this case is cleaning colorful cloth (not just cleaning). > > From an SO perspective, interface is the servant of the business functionality. We can twist interfaces in any way w/o changing business functions and RWE. In particular, a service may have as many interfaces as needed; the interfaces may be communication channel dependent, consumer audience dependent, automated or manual - this does not matter, they lead to the same business functions and RWE > > 5) though the principles are different, a service orientation can effectively use EDA principles for its purposes, opposite is not 100% true > > - Michael
