So, are you saying that MVC is in the small what SOA is in the large? And... how would you apply techniques for building SOA on technologies such as Ruby on Rails that tightly couple the View part of the architecture to a particular presentation form? I think the question begs a deeper consideration ;)

Ron

Keith Harrison-Broninski wrote:

Technically, the analogy is very simple:

Model = Component
View = Service
Controller = Middleware connecting the two (application server, ESB, etc)

-- 

All the best
Keith

http://keith.harrison-broninski.info


__________ NOD32 1.1663 (20060716) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com


__________ NOD32 1.1663 (20060716) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

-- 
_____________________________________________________________
Ronald Schmelzer
[EMAIL PROTECTED]
Senior Analyst
ZapThink LLC
Direct: 781-577-2779 / Main: 781-207-0203
__._,_.___


SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to