Skip to content

Concurrency

ARn edited this page May 8, 2016 · 1 revision
Concurrency in ARnActorModel

An Actor Model is geared toward Concurrency. This is true also in ARnActorModel, and this page explains how it works.

Any BaseActor or descendant object can be viewed as a stand-alone light thread :

  • it's activated at message reception
  • only one message can be processed at a time
  • it may receive messages from any other actors

On reception of a message, the actor is activated (the message is processed) and only one message is processed at a time. Any data covered by this actor will not be shared or called in a multi-threaded way. Using actors, behaviors and single-message process, concurrency is reached without needs for other traditionnal patterns (semaphore, lock, etc.)

Clone this wiki locally