> > One possibility for the technical delivery aspect of EDA is to simply > > pick one of the leading messaging/ESB solutions. Every one of them > > has pros and cons and selecting one (or more) is likely to provide > > the functions you'll need. MQ. AQ. MSMQ. Sonic. Fiorano. webMethods. > > TIBCO. (I'm violating my own peeve by listing companies instead of > > products, but you get the idea.) > > > > Alas, I'm not sure any of the products today will give you the > > universal standard you may be seeking and you'll may end up with > > messaging bridges regardless of which product suite you go with. > > Unless of course you choose the standard piece for messaging that is > going around (forget the name at the moment as its late) or of course > the grand-daddy of them all MQSeries which runs on everything and > everyone seems to interop with it.
"standard piece for messaging" -> you mean AMQP? That's work on progress, far from usable standar today. > If you are using JMS (and I have no idea why you wouldn't) I need (i'm looking for) "universal" interoperability, i.e., in my scenario participants may use java, .net, python, etc. I'm in a B2B (G2G actually) scenario. More precisely, i'm trying to design the model for services/events exposition and consumption in a very "decentralized" B2B network. For the services part i'll choose Web Services (WS-I compliant). The problem is with the "events" part. ¿Someone is using Atom/RSS? I like the simpliciy of that approach. Maybe the pull model is right for me (universal interoperability, multiplatform and simplicity are more important requirements). Regards.
