hmbdc is an open source headers only C++ framework and library built on top of various real-world tested lockfree algorithms that facilitate ultra low latency and high throughput messagin (inter-thread, inter-process and thru network) programming. It aims to take most out of the allocated hardware resources (memory, cores, NICs and switches) to achieve latency and throughput goals. It works as a framework but it can also be used as libraries to collaborate with other frameworks or extend existing middleware capability with 'zero-copy', 'reliable multicast', 'kernel bypassing' etc, etc.

Keywords and features:

• Supports x86_64, aarch64, Linux, gcc(>=8.4.1), clang(>=10)and QNX/qcc(>=11, beta)
• multithreaded without the headache
• low latency / high throughput / supports kernel bypassing (via netmap drivers)
• support multiple types of transport mechanisms with the consistent look and feel C++17 API: interthread interprocess UDP multicast TCP netmap multicast reliable multicast reliable netmap
• support easy to use symetric (no broker process) C++ type based message (both reliable and latest only) publish / subscribe with automatic pub/sub topology visualization and message recording / playback tools
• other high performance computing features: high speed async logging, timer, rate control ...
• straightforward integration with any other programming languages that supports Linux piping
• provide performance measurement tools

• it is used in areas that are cpu / network intensive with high performance (latency / throughput) requirements such as high frequency trading, high performance server-backend, robotics, distributed real-time systems, etc. hmbdc helps you get it done quick and fast.

hmbdc offers both C++ Type Inferred Pub/Sub (TIPS) and the higher level Pub/sub On String Topics(POTS). You can either publish in form of C++ types or in form of bytes on different topics. Here is an example pub/sub topology automatically generated from C++ code:

Serialization/copying is only performed when it is absolutely necessary. The key concepts are Node and Domain

The communications within local host nodes are automatically carried out via shared memory. On top of that, user can also opt to use zero-copy messages to acheive the best latecy for communicating large messages between Nodes on the same host.

• Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz 8 core 16G RAM, CentOs8
• Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Ubuntu 18.04
• 1G CISCO SG200 switch (intel 82574L and 82579LM NIC)
• All results are also compared with qperf in the same enviroment

See perf-sample.txt

hmbdc design uses a mix of OO and C++ generic programming:

API are in doxygen format.

0. make sure you have the required lib in place: boost-dev package; (make sure you have the QNX or aarch64 cross compiling tools ready if you are building for them. for QNX, source the qnx set env script now)
1. in hmbdc root dir, type make

• MIT Licensed
• please direct questions to [email protected] and thank you for your interests in hmbdc!

• build qnx / aarch64 version of boost ./b2 toolset=qcc target-os=qnxnto threadapi=pthread link=static -l240 --layout=system --without-python cxxflags="-V gcc_ntox86_64_gpp -Wc,-std=gnu++0x -D_LITTLE_ENDIAN" linkflags="-V gcc_ntox86_64_gpp -lang-c++"