4 ms·
(Disclaimer: CAF co-maintainer here.) It's great to see more actor runtimes on the rise. Also interesting to see the actor model implemented in Go, which follo
by mavam 10y ago
(Disclaimer: CAF co-maintainer here.)
It's great to see more actor runtimes on the rise. Also interesting to see the actor model implemented in Go, which follows more of a pi calculus design with its channels. With an actor design, the software architecture shifts towards the endpoints of the communication.
CAF targets the performance-sensitive C++ community, so sending a message in the same process only costs a single hardware-support CAS operation. We found this scales very well. No GC other than reference counting.
For those interested in learning more about actors in the C++ ecosystem, I recently gave a talk about CAF and some performance comparisons to other frameworks in various scenarios:
http://matthias.vallentin.net/slides/caf-rise.pdf http://matthias.vallentin.net/slides/caf-rise.pdf
- alexeiz 10y agoI've been using the CAF library for a while, and the experience so far has been very positive. It's surprisingly capable and flexible at the same time. The use of modern C++ in CAF makes your code very clean and idiomatic. Other C++ libraries of this kind are usually quite painful to use (because you know, most people think if it's C++ it has to be hard). CAF is a pleasant exception to this rule.