As far as I understand the Actor Model and the Reactive Programming are separate concepts. Actor Model does not seem to be inherently reactive to me.

However the Akka framework which is an Actor Model implementation is being described as reactive:

"Java and Scala program logic lives in lightweight Actor objects, which send and receive messages in a reactive fashion."

"We Are Reactive"

Is it a case of misusing the term or they are completely correct? Is any actor model implementation (e.g. Erlang) already reactive? Is simply generating messages as a response to other messages considered reactive as well?

Some related reading where the approaches are contrasted:


They don't mean reactive as in functional reactive programming, they mean reactive as in the reactive manifesto, which is a more generic term for a movement to build software that is event-driven, scalable, and resilient. It's a relative recent movement and the term hasn't really caught on.

  • I did not imply just the functional variant either. Just when I am reading the en.wikipedia.org/wiki/Reactive_programming description nothing screams "yep, Actor Model is spot on to lead into the reactive pit of success". – Den Sep 1 '14 at 18:34

protected by gnat Mar 25 '17 at 20:53

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.