so5-dining-philosophers
Several implementations of solutions for "Dining Philosophers" problem built by using Actor and CSP models on top of SObjectizer framework (by Stiffstream)
Disruptor-cpp
Port of LMAX Disruptor to C++ (by Abc-Arbitrage)
| so5-dining-philosophers | Disruptor-cpp | |
|---|---|---|
| 1 | 1 | |
| 1 | 337 | |
| - | 2.7% | |
| 0.0 | 0.0 | |
| over 2 years ago | over 1 year ago | |
| C++ | C++ | |
| - | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
so5-dining-philosophers
Posts with mentions or reviews of so5-dining-philosophers.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-11.
-
What are some candidate libraries for inter-thread communication like message boxes or event systems?
I want to note that SObjectizer provides not only agents and dispatchers for them, there is also such a thing as message chains. They were introduced specially for the integration of non-SObjectizer-parts of an application with SObjectizer-part. But since then they grew to a full-fledged mechanism of building multithreading applications even without agents. You can take a look at our dining-philosophers demo (the description, the repository).
Disruptor-cpp
Posts with mentions or reviews of Disruptor-cpp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-11.
-
What are some candidate libraries for inter-thread communication like message boxes or event systems?
If low latency / performance is important then something like aeron: https://github.com/real-logic/aeron or the disruptor pattern: https://github.com/Abc-Arbitrage/Disruptor-cpp are good options. Aeron supports network message but requires a driver to be running on the system even for IPC. Disruptor is thread to thread messaging only and doesn't need drivers etc - just a normal library.
What are some alternatives?
When comparing so5-dining-philosophers and Disruptor-cpp you can also consider the following projects:
mosquitto_transport - mosquitto_transport is an experiment of writing SObjectizer-based wrapper around mosquitto library.
Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport
sobjectizer - An implementation of Actor, Publish-Subscribe, and CSP models in one rather small C++ framework. With performance, quality, and stability proved by years in the production.
benchmarks - Latency benchmarks for messaging
RxCpp - Reactive Extensions for C++
Rx.NET - The Reactive Extensions for .NET
BlockingCollection - C++11 thread safe, multi-producer, multi-consumer blocking queue, stack & priority queue class
rotor - Event loop friendly C++ actor micro-framework, supervisable
mqtt_cpp
so5-dining-philosophers vs mosquitto_transport
Disruptor-cpp vs Aeron
so5-dining-philosophers vs sobjectizer
Disruptor-cpp vs benchmarks
so5-dining-philosophers vs RxCpp
Disruptor-cpp vs Rx.NET
so5-dining-philosophers vs BlockingCollection
Disruptor-cpp vs rotor
so5-dining-philosophers vs mqtt_cpp
Disruptor-cpp vs BlockingCollection
so5-dining-philosophers vs rotor
Disruptor-cpp vs RxCpp