Mark, Anne, I think Anne referred to the view of SOA being a methodology for deciding what the services are one should create for a particular environment (enterprise). E.g. "If you have a Content Management System that makes use of data owned/managed by other application SOA provides the guideline that you should see the CMS as a service that the other applications can export data to. Opposed to building message queue that you dump any data in that is new or has changed without considering the actual recipient.
Weak example IMO, sorry. Jan On Sep 8, 2008, at 4:28 PM, Mark Baker wrote: > On Mon, Sep 8, 2008 at 8:57 AM, Anne Thomas Manes > <[EMAIL PROTECTED]> wrote: >> Correct, Mark. These are principles, not constraints. >> >> SOA operates at a higher level than REST. (My apologies to Rob.) SOA >> defines principles that should be applied when determining what to >> build. It doesn't give you very much advice as to how to build it. >> REST defines constraints that should be applied when determining how >> to build it. > > I think a lot of people would disagree with you, Anne. SOA is often > referred to as an architectural style. > > Besides, at that level, SOA would be comparable/synonymous with > "software architecture", which makes little sense to me. > > Mark. > > ------------------------------------ > > Yahoo! Groups Links > > > -- Jan Algermissen INTAKI . http://www.intaki.com/
