> > As an abstract concept, messaging is fine, but this usually
> > implies a particular technology.
>
> Looking at what Andrew Townley, et al. have done with Reach, I think
> they've addressed this concern and the standards thing very well.
Thanks for the sentiment, Patrick, but I can hardly take too much of the
credit. I wrote some documents, but there was a whole lot of this stuff
done before I got there.
What we have isn't as clean as I'd like in places. Some of the things
I've tried to introduce in the current versions of rig0007 (which now
has examples/reference implementations, btw), rig0019 and rig0100 are
steps in the right direction, but from an operational perspective, we're
not quite there yet.
I understand why some of the original decisions about reliability (in
our case ACK/NACK messages) were made, but how far do you go with
reliability and at how many layers? At the moment, I think we should be
gravitating more towards a SNMP style of asynchronous messaging with
reliable transfer protocols between each step as is reflected in the
current documents, but then if you ever want to leverage unreliable
transfer protocols, you're in trouble. Fortunately, RRMTP seems to be
looking good so far as a lightweight, reliable transfer protocol that's
easy to implement, but our "real" implementation is currently in the
final rounds of testing and not yet deployed.
We are fairly unique in the approach we've taken based on what I see
when I talk to other people trying to get their heads around SOA or who
are currently implementing it, and I think a lot of what we're doing is
ahead of some of the thinking out there. However, it doesn't apply in
all cases. Change any one of the fundamental assumptions within the
environment and all bets are off.
As a bit of an exercise to try and apply what I've learned so far, I'm
trying to figure out the best hybrid approach between what I would
consider the two extremes I've seen, ours and the SOAP-centric WSA,
might be. There's also WOA or "pure REST" to consider as well, and I
have some ideas on bringing them all together. However, I haven't been
thinking seriously about it enough yet to have any concrete thoughts.
I'll keep you posted... ;)
ast
***************************************************************************************************
The information in this email is confidential and may be legally privileged Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
***************************************************************************************************
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.
