nanomsg alternatives and similar libraries
Based on the "Inter-process communication" category.
Alternatively, view nanomsg alternatives based on common mentions on social networks and blogs.
gRPC9.9 9.9 L3 nanomsg VS gRPCThe C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
Apache Thrift9.4 9.5 L1 nanomsg VS Apache ThriftApache Thrift
ZeroMQ9.2 5.9 L2 nanomsg VS ZeroMQZeroMQ core engine in C++, implements ZMTP/3.1
Cap'n Proto9.1 8.6 L1 nanomsg VS Cap'n ProtoCap'n Proto serialization/RPC system - core tools and C++ library
rpclib6.6 2.5 L1 nanomsg VS rpclibrpclib is a modern C++ msgpack-RPC server and client library
libjson-rpc-cpp5.8 0.0 L3 nanomsg VS libjson-rpc-cppC++ framework for json-rpc (json remote procedure call)
AREG SDK3.1 5.3 nanomsg VS AREG SDKInterface-centric, cross-platform communication engine that simplifies multiprocessing and multithreading application development.
simple-rpc-cpp1.7 0.0 L4 nanomsg VS simple-rpc-cppa simple RPC wrapper generator to C/C++ functions
eCAL0.8 9.2 nanomsg VS eCALPlease visit the new repository: https://github.com/eclipse-ecal/ecal
xmlrpc-cA lightweight RPC library based on XML and HTTP. [BSD]
WAMPProvides RPC and pub/sub messaging patterns. (various implementations, various languages)
Write Clean C++ Code. Always.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of nanomsg or a related project?
Welcome to nanomsg
The nanomsg library is a simple high-performance implementation of several "scalability protocols". These scalability protocols are light-weight messaging protocols which can be used to solve a number of very common messaging patterns, such as request/reply, publish/subscribe, surveyor/respondent, and so forth. These protocols can run over a variety of transports such as TCP, UNIX sockets, and even WebSocket.
For more information check the website.
- Windows Vista or newer (Windows XP and 2003 are NOT supported)
- Microsoft Visual Studio 2010 (including C++) or newer, or mingw-w64. (Specifically mingw and older Microsoft compilers are NOT supported, and we do not test mingw-w64 at all, so YMMV.)
- CMake 2.8.12 or newer, available in $PATH as
POSIX (Linux, MacOS X, UNIX)
- ANSI C compiler supporting C89
- POSIX pthreads (should be present on all modern POSIX systems)
- BSD sockets support for both TCP and UNIX domain sockets
- CMake (http://cmake.org) 2.8.12 or newer, available in $PATH as
- asciidoctor (http://asciidoctor.org/) available as
- If not present, docs are not formatted, but left in readable ASCII
- Available on-line at http://nanomsg.org/documentation
- asciidoctor (http://asciidoctor.org/) available as
Quick Build Instructions
These steps here are the minimum steps to get a default Debug build. Using CMake you can do many other things, including setting additional variables, setting up for static builds, or generation project or solution files for different development environments. Please check the CMake website for all the various options that CMake supports.
This assumes you have a shell in the project directory, and have the cmake and suitable compilers (and any required supporting tools like linkers or archivers) on your path.
% mkdir build
% cd build
% cmake ..
% cmake --build .
% ctest .
% sudo cmake --build . --target install
% sudo ldconfig(if on Linux)
This assumes you are in a command or powershell window and have
the appropriate variables setup to support Visual Studio, typically
vcvarsall.bat or similar with the appropriate argument(s).
It also assumes you are in the project directory.
cmake --build . --config Debug
ctest -C Debug .
cmake --build . --config Debug --target installNB: This may have to be done using an Administrator account.
Alternatively, you can build and install nanomsg using vcpkg dependency manager:
git clone https://github.com/Microsoft/vcpkg.git
./vcpkg integrate install
./vcpkg install nanomsg
The nanomsg port in vcpkg is kept up to date by microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg repository.
We normally build a dynamic library (.so or .DLL) by default.
If you want a static library (.a or .LIB), configure by passing
-DNN_STATIC_LIB=ON to the first
POSIX systems will need to link with the libraries normally used when building network applications. For some systems this might mean -lnsl or -lsocket.
You will also need to define
NN_STATIC_LIB in your compilation environment
when building programs that use this library. This is required because of
the way Windows changes symbol names depending on whether the symbols should
be exported in a DLL or not.
When using the .LIB on Windows, you will also need to link with the ws2_32, mswsock, and advapi32 libraries, as nanomsg depends on them.
This library is considered to be in "sustaining" mode, which means that new feature development has ended, and bug fixes are made only when strictly necessary for severe issues.
New development is now occurring in the NNG project, which offers both protocol and API compatibility with this project. Please consider using NNG for new projects.
Please see the file SUPPORT for more details.
*Note that all licence references and agreements mentioned in the nanomsg README section above are relevant to that project's source code only.