[DeepDive] Event Systems, Actors, etc

CloudEvents

https://en.wikipedia.org/wiki/Actor_model
- The actor model in computer science is a mathematical model of concurrent computation that treats actor as the universal primitive of concurrent computation. In response to a message it receives, an actor can: make local decisions, create more actors, send more messages, and determine how to respond to the next message received. Actors may modify their own private state, but can only affect each other indirectly through messaging (removing the need for lock-based synchronization).

https://akka.io/
https://github.com/akka/akka
- Build highly concurrent, distributed, and resilient message-driven applications on the JVM

https://github.com/AsynkronIT/protoactor-go
- Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin

http://actor-framework.org/
- An Open Source Implementation of the Actor Model in C++
https://github.com/actor-framework/actor-framework
- CAF is an open source implementation of the actor model for C++ featuring lightweight & fast actor implementations, pattern matching for messages, network transparent messaging, and more.

https://github.com/actix/actix
- Actor framework for Rust
https://riker.rs/ -> A Rust framework for building modern, concurrent and resilient applications
- https://github.com/riker-rs/riker/
- Easily build efficient, highly concurrent and resilient applications. An Actor Framework for Rust.

https://www.reactivemanifesto.org/
- Message Driven: Reactive Systems rely on asynchronous message-passing to establish a boundary between components that ensures loose coupling, isolation and location transparency. This boundary also provides the means to delegate failures as messages. Employing explicit message-passing enables load management, elasticity, and flow control by shaping and monitoring the message queues in the system and applying back-pressure when necessary. Location transparent messaging as a means of communication makes it possible for the management of failure to work with the same constructs and semantics across a cluster or within a single host. Non-blocking communication allows recipients to only consume resources while active, leading to less system overhead.
https://en.wikipedia.org/wiki/Event-driven_programming
- In computer programming, event-driven programming is a programming paradigm in which the flow of the program is determined by events such as user actions (mouse clicks, key presses), sensor outputs, or messages from other programs or threads.
https://github.com/EventEmitter2/EventEmitter2
- EventEmitter2 is an implementation of the EventEmitter module found in Node.js. In addition to having a better benchmark performance than EventEmitter and being browser-compatible, it also extends the interface of EventEmitter with many additional non-breaking features.