ZMQ is great...

Jump to bottom Edit New page

hyperletter edited this page Nov 13, 2012 · 4 revisions

... at least it is in some scenarios.

ZMQ is great for pushing messages extremely fast but its not easy to monitor how things are going under the surface.

Here is a compassion which we hope to convince you to see Hyperletter as an alternative to ZMQ.

ZMQ

Pros

FAST!@#
Used by many
Many language bindings
Different protocols (TCP/IP, PGM, etc)

Cons

Hard to monitor
Many different socket types
Internal queue strategy
If a socket (PUSH for example) is connected to two other sockets (PULL for example) and one PULL-socket goes down. ZMQ will keep queuing dead queue in case it will come back.
You have to do your own threading
DLL depends on X86/X64 platform
You have to do your own security

Hyperletter

Pros

Relatively fast
Per message (letter) security
Software ACK
Re-queue on failure
Per message multicast
All messages, even multicast, is dual-way
Just two socket types
HyperSocket
TypedHyperSocket
Events
Connecting
Connected
Disconnected
Sent
Requeued
Received
No X86/X64 problems

Cons

Only a .NET-binding (so far)
Not big community as ZMQ
Only TCP/IP