--- Gervas Douglas <[EMAIL PROTECTED]> wrote:
> You may all recall that I have raised the question of possible > Alternatives to WS Standards for implementing a SOA a couple of > times. > The main ones proffered so far have been REST, people and flying > monkeys. Gregg, this is the closest that any one has come to > positing > those Orphan Java technologies, Jini and JERI (I wonder, BTW, what > Walt Disney could do with these names??) as an alternative. As alternatives, I'm sure there are plenty in vendors and large IT organizations that would also position: - proprietary messaging with a JMS binding for interop - EJB 3 / RMI over IIOP (I have customers that continue to swear by it) - batch files - EDI AS1 or AS2 Or a mix of all of the above. As others have said, there are two conceptions SOA's out there... with "business SOA", the importance isn't with the mechanism, it's so one can generate agreement on certain constraints (e.g. service levels, funding, versioning, extensibility, data formats, schema definitions, and transfer semantics) and have a productive way to enforce those constraints. If one was going to truly use SOA as a focused approach to EA for an organization, one likely would have to mix and match all of the above in their plans and understand what agencies in the organization should use which approach, what elements should remain consistent across them, and what differences can or should be mediated across agencies. REST happens to be interesting as it embeds constraints right in the architectural style and seems to be designed to work within an anarchist model. Most other SOA directions seem to be leaning to a constitutional monarchy or federalist model. Cheers Stu __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
