areg-sdk
ZeroMQ
areg-sdk | ZeroMQ | |
---|---|---|
21 | 18 | |
238 | 9,274 | |
- | 1.4% | |
8.6 | 7.5 | |
about 1 month ago | 8 days ago | |
C++ | C++ | |
Apache License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
areg-sdk
-
Essentials of Object Oriented and Functional Programming: A Guide to Modular Code
FP Libraries: gRPC, ZeroMQ, and AREG are examples of libraries with a special focus on providing possibilities for Interprocess Communication. Developed using C++, they facilitate communication through predefined APIs, emphasizing functional programming concepts.
-
How to find a suitable topic at GitHub to contribute?
In addition, if the owners of the repositories add more relevant and precise labels to the issues, it increases the possibility that the OSS developers find the issues they would loved to resolve. For example, the issues of AREG SDK which marked "help wanted" in addition have such labels like "C++" or "cmake", "unit test", etc.
-
Makefile versus CMake build system
My closer introduction with these 2 tools started from OSS areg sdk project. Because of some experienced friend recommendation, i started with make. The main reason was that it is more spread in embedded. No other weighty argument they had. After having make, i decided to integrate cmake. Suddenly i figured out that cmake for me is more understandable and powerful. It already has many features that makes things easier. The biggest advantage for me is that in comparison to make / Makefile, lot of IDE support build with cmake. The cross-platform / cross-compile for areg-sdk is important feature, and this is easier to achieve with cmake. For example, I can compile with make under Linux with gcc/clang, but under windows can compile in cygwin environment and not with MSVC, which is not the issue in case of cmake.
-
Your fun software projects
Project: AREG is a cross-platform interface-centric lightweight communication engine, which forms a grid of services in the IoT fog- and mist-network, automates the real-time transmission of data between multiple connected software nodes, so that the connected Things interact like a thin distributed servers and clients. Technologies: C/C++17, standard library dependencies, POSIX and Win32 API. Can be used in real product.
-
How abut open source projects?
Nice. I also have own project, but it already requires much time, so that cannot join in other projects. As well, up to now have no dependencies, except standard system libraries. I think, we should have a separate post to share projects and give short description. Some might be interested to join.
- Cross-platform IPC engine that automates real-time data transmission between connected processes, allowing them to interact like a distributed services
- Distributed services programming for Embedded, IoT edge and desktop applications
- Interface-centric Object RPC (ORPC) engine for embedded and desktop
-
ncurses and POSIX
Here I've crated a list of API that use in the project. Some of methods are part of ncurses.h. So I have a questions:
ZeroMQ
-
Lightweight and fast AMQP (0-9-1) server
Slightly OT:
Are ZeroMQ and NanoMQ still widely used (and recommended)?
https://github.com/zeromq/libzmq
https://github.com/nanomq/nanomq
-
ZeroMQ – Relicense from LGPL3 and exceptions to MPL 2.0
Remarkable, up until recently, requests for a new release were sumewhat brusquely rejected and marked as spam.
https://github.com/zeromq/libzmq/issues/4455
I wonder what made the maintainer change his mind.
-
Essentials of Object Oriented and Functional Programming: A Guide to Modular Code
FP Libraries: gRPC, ZeroMQ, and AREG are examples of libraries with a special focus on providing possibilities for Interprocess Communication. Developed using C++, they facilitate communication through predefined APIs, emphasizing functional programming concepts.
-
A Modern High-Performance Open Source Message Queuing System
Unlikely, but they seem to be different things altogether. BlazingMQ appears to be a traditional message queue (think ActiveMQ), with message peristence. ZeroMQ is more of a network middleware (think Tibco Rendezvous), and does not include persistence.
BlazingMQ also appears to be more of a "platform" or "service" that an app can use (sort of like Oracle, say) -- ZeroMQ includes libraries that one can use to build an app, service or platform, but none is provided "out of the box".
Which makes it harder to get started with ZeroMQ, since by definition every ZeroMQ app is essentially built "from scratch".
If you're interested in ZeroMQ, you may want to check out OZ (https://github.com/nyfix/OZ), which is a Rendezvous-like platform that uses the OpenMAMA API (https://github.com/finos/OpenMAMA) and ZeroMQ (https://github.com/zeromq/libzmq) transport to provide a full-featured network middleware implementation. OZ has been used in our shop since 2020 handling approx 50MM high-value messages per day on our global FIX network.
-
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
What are some alternatives?
iceoryx - Eclipse iceoryx™ - true zero-copy inter-process-communication
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
nanomsg - nanomsg library
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
zenoh - zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks.
erpc - Embedded RPC
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
zmesh - Marching Cubes & Mesh Simplification on multi-label 3D images.
Apache Thrift - Apache Thrift
uTensor - TinyML AI inference library
Chronicle Queue - Micro second messaging that stores everything to disk