[zeromq-dev] data collector pattern

Stephen Hemminger shemminger at vyatta.com
Tue Mar 20 15:49:53 CET 2012


The guide is full of wonderful and useful cases, but there is one that appears
to be missing. For some applications there are lots of clients generating and one collector.
The clients typically generate data like statistics or information (like a temperature sensor)
that occurs periodically.  Each message from the client is idempotent and supersedes
the last one, therefore it is acceptable for the collector to miss one. This is sort of
the inverse of PUB-SUB.

What is the best way to do this kind of lossy data collection and still scale. The slow
way would be to use request/reply. Another awkward method would be to have the collector
subscribe to all the clients, but that requires an out of band protocol to find the client
endpoints. Pgn also works but requires that PGM protocol work in the network.

Maybe some combination of ROUTER-DEALER?



More information about the zeromq-dev mailing list