SaaSHub helps you find the best software and product alternatives Learn more →
ZeroMQ Alternatives
Similar projects and alternatives to ZeroMQ
-
-
NATS
High-Performance server for NATS.io, the cloud and edge native messaging system.
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
-
-
-
-
-
Sonar
Write Clean C++ Code. Always.. Sonar helps you commit clean C++ code every time. With over 550 unique rules to find C++ bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
-
loki-network
Lokinet is an anonymous, decentralized and IP based overlay network for the internet.
-
eCAL
Please visit the new repository: https://github.com/eclipse-ecal/ecal (by continental)
-
-
-
GameNetworkingSockets
Reliable & unreliable messages over UDP. Robust message fragmentation & reassembly. P2P networking / NAT traversal. Encryption.
-
-
-
-
-
comms_champion
C++(11) library to implement and tools to monitor binary communication protocols
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
ZeroMQ reviews and mentions
-
need xbps-src help
-- Using src='https://github.com/zeromq/libzmq/releases/download/v4.3.4/zeromq-4.3.4.tar.gz'
-
What network messaging library do you recommend?
Just check copying file in source repo https://github.com/zeromq/libzmq
-
What they don't teach you about sockets
I think the situation is more subtle than the poster admits.
No, ZeroMQ and successors do not tell you about socket state. You can't detect disconnection or reconnection. But then if a TCP connection fails in some way that does not lead to disconnection (packets getting dropped, remote machine powers down), it can't possibly tell you about that either, but you still need to deal with it. So in any case, you need some sort of application-level error detection and recovery; you need heartbeats, and serial numbers in messages, and a protocol for explicitly restarting a connection and performing the initial handshake. And once you have that, explicit connection events from ZeroMQ are much less important.
Admittedly, given that this is a TCP transport, reporting reconnections would still be useful, because TCP won't ever drop messages from the interior of a sequence itself (if it delivers 15, it has delivered 1 - 14 already), so you shouldn't need the serial numbers.
And if it's really not possible to detect authentication failures, than that seems rubbish. And it seems that is indeed the case: https://github.com/zeromq/libzmq/issues/3505
- Encryption using ZMQ: How to handle certificates?
-
Any good lightweight c++ local socket library for embedded Linux?
From https://github.com/zeromq/libzmq
Maybe I am not understanding it correctly, the https://github.com/zeromq/libzmq is GPL v3, and header only file is https://github.com/zeromq/cppzmq MIT license? So I can use the header only library and I don't need to open source my code?
- can you recommend a production level C++ open source project that I can learn what is the production level code looks like?
-
A note from our sponsor - #<SponsorshipServiceOld:0x00007fea5982b338>
www.saashub.com | 1 Feb 2023
Stats
zeromq/libzmq is an open source project licensed under GNU General Public License v3.0 only which is an OSI approved license.