> > I'm just wondering if this is not "yet another passing trend", > like ESB (Enterprise Service Buses) was a few years ago... (Actually > they've promised exactly the same, but I think the frontend library > was presented as a SOAP based web service.) >
NYSE strongly supports MAMA. It can be found in many of their products. http://nysetechnologies.nyx.com/sites/technologies.nyx.com/files/Market-Data-Platform-V5-Product-Sheet_0.pdf http://nysetechnologies.nyx.com/data-technology/superbook http://nysetechnologies.nyx.com/sites/technologies.nyx.com/files/SuperBook-product-sheet-web.pdf http://nysetechnologies.nyx.com/data-technology/supertrade http://nysetechnologies.nyx.com/sites/technologies.nyx.com/files/L5718_NYSE%20Tech%20SuperTrad_OST_Final.pdf If ZeroMQ wants to compete harder in this area, the MAMA as soon as possible should be supported. This is an opportunity for ZeroMQ. regards, Daniel > Ciprian. > > >> 2011/11/2 Ciprian Dorin Craciun <[email protected]> >>> >>> 2011/11/2 Daniel Cegiełka <[email protected]>: >>> > >>> > How OpenMAMA Works >>> > >>> > OpenMama uses a common publish/subscribe idiom (pub/sub). In this >>> > messaging >>> > pattern the messages are not sent directly to the receivers, but published >>> > to a topic. Subscribers express interest in one or more topic, and receive >>> > only messages that concern them. This decoupling of publishers and >>> > subscribers allows for greater scalability. >>> > >>> > [...] >>> >>> >>> Now maybe this is a little off-topic -- although the initial >>> developers of ZeroMQ also developed the first version of AMQP (if I >>> recall correctly???) -- but here it goes... :) >>> >>> Now when I've first seen AMQP I've said: "finally a protocol which >>> is both simple, flexible and implementable"... (Unfortunately each >>> broker is still compatible only with the "sanctioned" libraries...) >>> But still, AMQP was born from the shortcomings of existing solutions, >>> especially JMS, which was API based, not protocol based, and I had >>> high hopes... (Currently I use both RabbitMQ and ZeroMQ for different >>> purposes.) >>> >>> So from what I've seen on OpenMAMA page, they go back to an API >>> based standard, thus allowing API "extensions" to cripple any window >>> of portability... Why??? (It's just like instead of having HTTP, IETF >>> would have defined an API and made it "pluggable"...) >>> >>> (I would love to hear the opinion of other ZeroMQ developers and >>> users on this topic.) >>> >>> Thanks, >>> Ciprian. >>> _______________________________________________ >>> zeromq-dev mailing list >>> [email protected] >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
