|libev||C++ Actor Framework|
|over 1 year ago||8 days ago|
|GNU General Public License v3.0 or later||BSD 3-clause "New" or "Revised" License|
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.
2 projects | reddit.com/r/badcode | 24 Mar 2022
C in Web Dev
5 projects | reddit.com/r/C_Programming | 4 Dec 2021
Ideas, thoughts, and notes on an action based polymorphism pattern for C
2 projects | reddit.com/r/C_Programming | 3 Jun 2021
It's done even now. See ev.h where they do this. Just that you disable GCC's aliasing warning. There's a reason why restrict and aliasing became important to deal with. It wasn't standards that killed it.
C++ Actor Framework
Actor system for the JVM developed by Electronic Arts
6 projects | news.ycombinator.com | 28 Apr 2022
I'd like to mention the native actor model implementation CAF, the C++ Actor Framework, and share some experiences. (Disclaimer: I've been developing on CAF in the past and have a good relationship with the creator.) CAF (1) provides native actors without an VM layer, (2) type-safe interfaces so that the compiler yells at you when a receiver cannot handle a message, and (3) transparent copy-on-write messaging so that you can still push stuff through pipelines and induce only copies only when a ref count is greater than one.
In our telemetry engine VAST, we've been using CAF successfully for several years for building a distributed system that always has a saturated write path. CAF provides a credit-based streaming abstraction as well, so that you can have backpressure across a chain of actors, making burst-induced OOM issues a blast from the past. You also get all the other benefits of actors, like linking and monitoring, to achieve well-defined failure semantics: either be up and running or collectively fail, but still allowing for local recovery—except for segfaults, this is where "native" has a disadvantage over VM-based actor models.
With CAF's network transparent runtime, a message ender doesn't need to know where receiver lives; the runtime either passes the message as COW pointer to the receiver or serializes it transparently. Other actor model runtimes support that as well, but I'm mentioning it because our experience showed that this is great value: we can can slice and dice our actors based on the deployment target, e.g., execute the application in one single process (e.g., for a beefy box) or wrap actors into single OS processes (e.g., when deploying on container auto-scalers).
The deep integration with the C++ type system allowed us to define very stable RPC-like interfaces. We're currently designing a pub/sub layer as alternate access path, because users are interested in tapping into streaming feeds selectively. This is not easy, because request-response and pub/sub are two ends of a spectrum, but it turns out we can support nicely with CAF.
- VAST: https://tenzir.github.io/vast/docs/understand-vast/actor-mod... (sorry for the incompleteness, we're in migration mode from the old docs, but this page is summarizing the benefits of CAF for us best)
- Good general actor model background: http://dist-prog-book.com/chapter/3/message-passing.html#why...
C++ Jobs - Q2 2022
4 projects | reddit.com/r/cpp | 3 Apr 2022
VAST is a flight recorder and security content execution engine. On the one hand, there exists a continuous stream of high-volume data sources (such as network telemetry as NetFlow, Zeek, Suricata, and endpoint telemetry). On the other hand, VAST processes needle-in-haystack queries to provide answers to questions like "has this threat been relevant to us 8 months ago?", and supports threat hunters with an interactive query capability to explore the data. From an engineering perspective, we focus especially on the separation of read and write path, concurrent message passing in an actor model runtime (CAF), and leveraging open standards, like Apache Arrow, to establish a high-bandwidth data plane for sharing data with downstream tooling. A flexible plugin API enables additional security-specific use cases on top, such as realtime matching of threat intelligence or mining of asset data for passive inventorization.
C++ Jobs - Q4 2021
4 projects | reddit.com/r/cpp | 2 Oct 2021
Technologies: Apache Arrow, Flatbuffers, C++ Actor Framework, Linux, Docker, Kubernetes
What are some alternatives?
libuv - Cross-platform asynchronous I/O
libevent - Event notification library
Boost.Asio - Asio C++ Library
rotor - Event loop friendly C++ actor micro-framework, supervisable
Taskflow - A General-purpose Parallel and Heterogeneous Task Programming System
C++React - C++React: A reactive programming library for C++11.
moodycamel - A fast multi-producer, multi-consumer lock-free concurrent queue for C++11
uvw - Header-only, event based, tiny and easy to use libuv wrapper in modern C++ - now available as also shared/static library!
Thrust - The C++ parallel algorithms library.