Throwing away all of the problems solved by TCP improvements just invents old problems and new problems; let a messaging layer handle transport.
Throwing away all of the problems solved by TCP improvements just invents old problems and new problems; let a messaging layer handle transport.
How does using 0mq helps me with sending the data that's updated every second and I only need the latest value?
As far as I remember, 0mq queueing policy will end up in the same situation as the TCP queueuing policy: there's no way to tell 0mq, or TCP, that "only the last sent packet matters, not the previous ones".
And the fact is that the reason to use UDP is primarily for those data streams where queuing doesn't make any sense whatsoever in the first place.
And more importantly - have you actually used nanomsg/nnm/0mq or similar yourself? All of these are variations on (re-)implementing TCP over UDP anyway. Or if you're using TCP channels - then reimplementing TCP queueing on top of OS-TCP queueuing.
Essentially the issue with TCP is that it's based on queues, rather than having a callback that could simply poll the applicatio:n "hey - I couldn't yet send that data - do you have an update so that I could retry with the fresh one?"