[service-orientated-architecture] Trolling for flames

[Ron Schmelzer]

So, what exactly is architecture infrastructure? Aren't these two different things... does it make sense to even combine these two words together? Ron Anne Thomas Manes wrote: Gregg, A SOA infrastructure [sorry JP, but I think this term is useful] ought to support any type of communication style: synchronous vs asynchronous, request/response vs one-way, direct connection vs brokered, queued, pub/sub, Linda, etc. It's even better if the infrastructure is natively supported by most development platforms. I think this last point is the most serious downfall for J/JS. You had the luxury of developing your own communication infrastructure, and you chose to base it on J/JS. (I think this was a great decision for you.) Most organizations don't have that luxury, though. For them, software infrastructure development is not a core competency. So they buy it. And because a communication infrastructure is such a critcal component in their IT systems, they tend to buy it from solid, stable vendors -- IBM, Microsoft, BEA, Oracle, SAP, etc. None of these vendors provide native support for J/JS (or any Linda system for that matter). I've always been a big fan of Linda, but you must agree that it's a fringe technology. It's been around for ever, but never been a part of the mainstream. The key advantage I see for using SOAP as the foundation for SOA is that *everyone* provides native support for the technology. Anne On 3/14/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote: Anne Thomas Manes wrote: > I understand that the JERI stack opens J/JS up to allow integration with > other languages and protocols, but there are a number of features in J/JS > which are available only to Java applications. There are a number of Web services features that are only available to web services applications. Where is the line drawn to differentiate?  I am not sure what missing features you think are problematic or which would cause problems.  Can you share some specific concerns?  This is really an interesting issue for me. At some point, the technology of choice is visible in your SOA.  The proliferation of a technology into your software implementation is a technical/implementation issue which needs attention. Gregg Wonderly 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/ __________ NOD32 1.1431 (20060305) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com __________ NOD32 1.1431 (20060305) 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  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.