On Jul 7, 2006, at 1:10 PM, Anne Thomas Manes wrote: > But you can't ignore the data issue. The data is the essence of the > application semantics. > > Anne
Anne, what Mark is saying (IMO) is that you can ignore the data issue for the comparision between the architectural styles, because in a SOA as well as in a REST system you have to integrate the data. When you use non/uniform interfaces you have to integrate the interfaces in addition. With REST there is no interface integration issue. Data integration is IMO a lot easier to accomplish than interface integration, usually a transformation should do. But there is another advantage that you just do not have with SOA: network effects combine with the use of the 80/20 principles IMHO can be used to increase the likelyhood that others don't roll their own data models and syntaxes but reuse existing ones (not necissarily from the Web, but also intra-organizational). The latter is so far the best solution I see to building systems that are effectively decentralized - when you cannot simply control the desig of all components (e.g. due to multiple admnistrative domains or in B2B scenarios). Again: integration does not go away, it just becomes easier and after all, cheaper! Jan ------------------------ Yahoo! Groups Sponsor --------------------~--> Something is new at Yahoo! Groups. Check out the enhanced email design. http://us.click.yahoo.com/SISQkA/gOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
