# Actor model

The actor model in computer science is a mathematical model of concurrent computation that treats "actors" as the universal primitives of concurrent computation. In response to a message that 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 through messages (avoiding the need for any locks).

The actor model originated in 1973.[1] It has been used both as a framework for a theoretical understanding of computation and as the theoretical basis for several practical implementations of concurrent systems. The relationship of the model to other work is discussed in Actor model and process calculi.

## History

According to Carl Hewitt, unlike previous models of computation, the actor model was inspired by physics, including general relativity and quantum mechanics[citation needed]. It was also influenced by the programming languages Lisp, Simula and early versions of Smalltalk, as well as capability-based systems and packet switching. Its development was "motivated by the prospect of highly parallel computing machines consisting of dozens, hundreds, or even thousands of independent microprocessors, each with its own local memory and communications processor, communicating via a high-performance communications network."[2] Since that time, the advent of massive concurrency through multi-core and manycore computer architectures has revived interest in the actor model.

Following Hewitt, Bishop, and Steiger's 1973 publication, Irene Greif developed an operational semantics for the actor model as part of her doctoral research.[3] Two years later, Henry Baker and Hewitt published a set of axiomatic laws for Actor systems.[4][5] Other major milestones include William Clinger's 1981 dissertation introducing a denotational semantics based on power domains[2] and Gul Agha's 1985 dissertation which further developed a transition-based semantic model complementary to Clinger's.[6] This resulted in the full development of actor model theory.

Major software implementation work was done by Russ Atkinson, Giuseppe Attardi, Henry Baker, Gerry Barber, Peter Bishop, Peter de Jong, Ken Kahn, Henry Lieberman, Carl Manning, Tom Reinhardt, Richard Steiger and Dan Theriault in the Message Passing Semantics Group at Massachusetts Institute of Technology (MIT). Research groups led by Chuck Seitz at California Institute of Technology (Caltech) and Bill Dally at MIT constructed computer architectures that further developed the message passing in the model. See Actor model implementation.

Research on the actor model has been carried out at California Institute of Technology, Kyoto University Tokoro Laboratory, MCC, MIT Artificial Intelligence Laboratory, SRI, Stanford University, University of Illinois at Urbana-Champaign,[7] Pierre and Marie Curie University (University of Paris 6), University of Pisa, University of Tokyo Yonezawa Laboratory, Centrum Wiskunde & Informatica (CWI) and elsewhere.

## Fundamental concepts

The actor model adopts the philosophy that everything is an actor. This is similar to the everything is an object philosophy used by some object-oriented programming languages.

An actor is a computational entity that, in response to a message it receives, can concurrently:

• send a finite number of messages to other actors;
• create a finite number of new actors;
• designate the behavior to be used for the next message it receives.

There is no assumed sequence to the above actions and they could be carried out in parallel.

Decoupling the sender from communications sent was a fundamental advance of the Actor model enabling asynchronous communication and control structures as patterns of passing messages.[8]

Recipients of messages are identified by address, sometimes called "mailing address". Thus an actor can only communicate with actors whose addresses it has. It can obtain those from a message it receives, or if the address is for an actor it has itself created.

The actor model is characterized by inherent concurrency of computation within and among actors, dynamic creation of actors, inclusion of actor addresses in messages, and interaction only through direct asynchronous message passing with no restriction on message arrival order.

## Formal systems

Over the years, several different formal systems have been developed which permit reasoning about systems in the actor model. These include:

There are also formalisms that are not fully faithful to the actor model in that they do not formalize the guaranteed delivery of messages including the following (See Attempts to relate Actor semantics to algebra and linear logic):

## Applications

The Actor model can be used as a framework for modeling, understanding, and reasoning about a wide range of concurrent systems. For example:

• Electronic mail (e-mail) can be modeled as an Actor system. Accounts are modeled as Actors and email addresses as Actor addresses.
• Web Services can be modeled with SOAP endpoints modeled as Actor addresses.
• Objects with locks (e.g., as in Java and C#) can be modeled as a Serializer, provided that their implementations are such that messages can continually arrive (perhaps by being stored in an internal queue). A serializer is an important kind of Actor defined by the property that it is continually available to the arrival of new messages; every message sent to a serializer is guaranteed to arrive.
• Testing and Test Control Notation (TTCN), both TTCN-2 and TTCN-3, follows actor model rather closely. In TTCN, Actor is a test component: either parallel test component (PTC) or main test component (MTC). Test components can send and receive messages to and from remote partners (peer test components or test system interface), the latter being identified by its address. Each test component has a behaviour tree bound to it; test components run in parallel and can be dynamically created by parent test components. Built-in language constructs allow the definition of actions to be taken when an expected message is received from the internal message queue, like sending a message to another peer entity or creating new test components.

## Message-passing semantics

The actor model is about the semantics of message passing.

### Unbounded nondeterminism controversy

Arguably, the first concurrent programs were interrupt handlers. During the course of its normal operation a computer needed to be able to receive information from outside (characters from a keyboard, packets from a network, etc). So when the information arrived the execution of the computer was "interrupted" and special code called an interrupt handler was called to put the information in a buffer where it could be subsequently retrieved.

In the early 1960s, interrupts began to be used to simulate the concurrent execution of several programs on a single processor.[15] Having concurrency with shared memory gave rise to the problem of concurrency control. Originally, this problem was conceived as being one of mutual exclusion on a single computer. Edsger Dijkstra developed semaphores and later, between 1971 and 1973,[16] Tony Hoare[17] and Per Brinch Hansen[18] developed monitors to solve the mutual exclusion problem. However, neither of these solutions provided a programming-language construct that encapsulated access to shared resources. This encapsulation was later accomplished by the serializer construct ([Hewitt and Atkinson 1977, 1979] and [Atkinson 1980]).

The first models of computation (e.g., Turing machines, Post productions, the lambda calculus, etc.) were based on mathematics and made use of a global state to represent a computational step (later generalized in [McCarthy and Hayes 1969] and [Dijkstra 1976] see Event orderings versus global state). Each computational step was from one global state of the computation to the next global state. The global state approach was continued in automata theory for finite state machines and push down stack machines, including their nondeterministic versions. Such nondeterministic automata have the property of bounded nondeterminism; that is, if a machine always halts when started in its initial state, then there is a bound on the number of states in which it halts.

Edsger Dijkstra further developed the nondeterministic global state approach. Dijkstra's model gave rise to a controversy concerning unbounded nondeterminism (also called unbounded indeterminacy), a property of concurrency by which the amount of delay in servicing a request can become unbounded as a result of arbitration of contention for shared resources while still guaranteeing that the request will eventually be serviced. Hewitt argued that the actor model should provide the guarantee of service. In Dijkstra's model, although there could be an unbounded amount of time between the execution of sequential instructions on a computer, a (parallel) program that started out in a well defined state could terminate in only a bounded number of states [Dijkstra 1976]. Consequently, his model could not provide the guarantee of service. Dijkstra argued that it was impossible to implement unbounded nondeterminism.

Hewitt argued otherwise: there is no bound that can be placed on how long it takes a computational circuit called an arbiter to settle (see metastability in electronics).[19] Arbiters are used in computers to deal with the circumstance that computer clocks operate asynchronously with respect to input from outside, e.g., keyboard input, disk access, network input, etc. So it could take an unbounded time for a message sent to a computer to be received and in the meantime the computer could traverse an unbounded number of states.

The actor model features unbounded nondeterminism which was captured in a mathematical model by Will Clinger using domain theory.[2] There is no global state in the actor model.[dubious ]

### Direct communication and asynchrony

Messages in the actor model are not necessarily buffered. This was a sharp break with previous approaches to models of concurrent computation. The lack of buffering caused a great deal of misunderstanding at the time of the development of the actor model and is still a controversial issue. Some researchers argued that the messages are buffered in the "ether" or the "environment". Also, messages in the actor model are simply sent (like packets in IP); there is no requirement for a synchronous handshake with the recipient.

### Actor creation plus addresses in messages means variable topology

A natural development of the actor model was to allow addresses in messages. Influenced by packet switched networks [1961 and 1964], Hewitt proposed the development of a new model of concurrent computation in which communications would not have any required fields at all: they could be empty. Of course, if the sender of a communication desired a recipient to have access to addresses which the recipient did not already have, the address would have to be sent in the communication.

For example, an Actor might need to send a message to a recipient Actor from which it later expects to receive a response, but the response will actually be handled by a third Actor component that has been configured to receive and handle the response (for example, a different Actor implementing the Observer pattern). The original Actor could accomplish this by sending a communication that includes the message it wishes to send, along with the address of the third Actor that will handle the response. This third Actor that will handle the response is called the resumption (sometimes also called a continuation or stack frame). When the recipient Actor is ready to send a response, it sends the response message to the resumption Actor address that was included in the original communication.

So, the ability of Actors to create new Actors with which they can exchange communications, along with the ability to include the addresses of other Actors in messages, gives Actors the ability to create and participate in arbitrarily variable topological relationships with one another, much as the objects in Simula and other object-oriented languages may also be relationally composed into variable topologies of message-exchanging objects.

### Inherently concurrent

As opposed to the previous approach based on composing sequential processes, the actor model was developed as an inherently concurrent model. In the actor model sequentiality was a special case that derived from concurrent computation as explained in actor model theory.

### No requirement on order of message arrival

Hewitt argued against adding the requirement that messages must arrive in the order in which they are sent to the Actor. If output message ordering is desired, then it can be modeled by a queue Actor that provides this functionality. Such a queue Actor would queue the messages that arrived so that they could be retrieved in FIFO order. So if an Actor X sent a message M1 to an Actor Y, and later X sent another message M2 to Y, there is no requirement that M1 arrives at Y before M2.

In this respect the actor model mirrors packet switching systems which do not guarantee that packets must be received in the order sent. Not providing the order of delivery guarantee allows packet switching to buffer packets, use multiple paths to send packets, resend damaged packets, and to provide other optimizations.

For example, Actors are allowed to pipeline the processing of messages. What this means is that in the course of processing a message M1, an Actor can designate the behavior to be used to process the next message, and then in fact begin processing another message M2 before it has finished processing M1. Just because an Actor is allowed to pipeline the processing of messages does not mean that it must pipeline the processing. Whether a message is pipelined is an engineering tradeoff. How would an external observer know whether the processing of a message by an Actor has been pipelined? There is no ambiguity in the definition of an Actor created by the possibility of pipelining. Of course, it is possible to perform the pipeline optimization incorrectly in some implementations, in which case unexpected behavior may occur.

### Locality

Another important characteristic of the actor model is locality.

Locality means that in processing a message, an Actor can send messages only to addresses that it receives in the message, addresses that it already had before it received the message, and addresses for Actors that it creates while processing the message. (But see Synthesizing Addresses of Actors.)

Also locality means that there is no simultaneous change in multiple locations. In this way it differs from some other models of concurrency, e.g., the Petri net model in which tokens are simultaneously removed from multiple locations and placed in other locations.

### Composing Actor systems

The idea of composing Actor systems into larger ones is an important aspect of modularity that was developed in Gul Agha's doctoral dissertation,[6] developed later by Gul Agha, Ian Mason, Scott Smith, and Carolyn Talcott.[9]

### Behaviors

A key innovation was the introduction of behavior specified as a mathematical function to express what an Actor does when it processes a message, including specifying a new behavior to process the next message that arrives. Behaviors provided a mechanism to mathematically model the sharing in concurrency.

Behaviors also freed the actor model from implementation details, e.g., the Smalltalk-72 token stream interpreter. However, it is critical to understand that the efficient implementation of systems described by the actor model require extensive optimization. See Actor model implementation for details.

### Modeling other concurrency systems

Other concurrency systems (e.g., process calculi) can be modeled in the actor model using a two-phase commit protocol.[20]

### Computational Representation Theorem

There is a Computational Representation Theorem in the actor model for systems which are closed in the sense that they do not receive communications from outside. The mathematical denotation denoted by a closed system S is constructed from an initial behavior S and a behavior-approximating function progressionS. These obtain increasingly better approximations and construct a denotation (meaning) for S as follows [Hewitt 2008; Clinger 1981]:

${\displaystyle \mathbf {Denote} _{\mathtt {S}}\equiv \lim _{i\to \infty }\mathbf {progression} _{{\mathtt {S}}^{i}}(\bot _{\mathtt {S}})}$

In this way, S can be mathematically characterized in terms of all its possible behaviors (including those involving unbounded nondeterminism). Although DenoteS is not an implementation of S, it can be used to prove a generalization of the Church-Turing-Rosser-Kleene thesis [Kleene 1943]:

A consequence of the above theorem is that a finite Actor can nondeterministically respond with an uncountable[clarify] number of different outputs.

### Relationship to logic programming

One of the key motivations for the development of the actor model was to understand and deal with the control structure issues that arose in development of the Planner programming language.[citation needed] Once the actor model was initially defined, an important challenge was to understand the power of the model relative to Robert Kowalski's thesis that "computation can be subsumed by deduction". Hewitt argued that Kowalski's thesis turned out to be false for the concurrent computation in the actor model (see Indeterminacy in concurrent computation).

Nevertheless, attempts were made to extend logic programming to concurrent computation. However, Hewitt and Agha [1991] claimed that the resulting systems were not deductive in the following sense: computational steps of the concurrent logic programming systems do not follow deductively from previous steps (see Indeterminacy in concurrent computation). Recently, logic programming has been integrated into the actor model in a way that maintains logical semantics.[19]

### Migration

Migration in the actor model is the ability of Actors to change locations. E.g., in his dissertation, Aki Yonezawa modeled a post office that customer Actors could enter, change locations within while operating, and exit. An Actor that can migrate can be modeled by having a location Actor that changes when the Actor migrates. However the faithfulness of this modeling is controversial and the subject of research.[citation needed]

### Security

The security of Actors can be protected in the following ways:

A delicate point in the actor model is the ability to synthesize the address of an Actor. In some cases security can be used to prevent the synthesis of addresses (see Security). However, if an Actor address is simply a bit string then clearly it can be synthesized although it may be difficult or even infeasible to guess the address of an Actor if the bit strings are long enough. SOAP uses a URL for the address of an endpoint where an Actor can be reached. Since a URL is a character string, it can clearly be synthesized although encryption can make it virtually impossible to guess.

Synthesizing the addresses of Actors is usually modeled using mapping. The idea is to use an Actor system to perform the mapping to the actual Actor addresses. For example, on a computer the memory structure of the computer can be modeled as an Actor system that does the mapping. In the case of SOAP addresses, it's modeling the DNS and the rest of the URL mapping.

### Contrast with other models of message-passing concurrency

Robin Milner's initial published work on concurrency[21] was also notable in that it was not based on composing sequential processes. His work differed from the actor model because it was based on a fixed number of processes of fixed topology communicating numbers and strings using synchronous communication. The original communicating sequential processes (CSP) model[22] published by Tony Hoare differed from the actor model because it was based on the parallel composition of a fixed number of sequential processes connected in a fixed topology, and communicating using synchronous message-passing based on process names (see Actor model and process calculi history). Later versions of CSP abandoned communication based on process names in favor of anonymous communication via channels, an approach also used in Milner's work on the calculus of communicating systems and the π-calculus.

These early models by Milner and Hoare both had the property of bounded nondeterminism. Modern, theoretical CSP ([Hoare 1985] and [Roscoe 2005]) explicitly provides unbounded nondeterminism.

Petri nets and their extensions (e.g., coloured Petri nets) are like actors in that they are based on asynchronous message passing and unbounded nondeterminism, while they are like early CSP in that they define fixed topologies of elementary processing steps (transitions) and message repositories (places).

## Influence

The actor model has been influential on both theory development and practical software development.

### Theory

The actor model has influenced the development of the Pi-calculus and subsequent Process calculi. In his Turing lecture, Robin Milner wrote:[23]

Now, the pure lambda-calculus is built with just two kinds of thing: terms and variables. Can we achieve the same economy for a process calculus? Carl Hewitt, with his Actors model, responded to this challenge long ago; he declared that a value, an operator on values, and a process should all be the same kind of thing: an Actor.
This goal impressed me, because it implies the homogeneity and completeness of expression ... But it was long before I could see how to attain the goal in terms of an algebraic calculus...
So, in the spirit of Hewitt, our first step is to demand that all things denoted by terms or accessed by names--values, registers, operators, processes, objects--are all of the same kind of thing; they should all be processes.

### Practice

The actor model has had extensive influence on commercial practice. For example, Twitter has used actors for scalability.[24] Also, Microsoft has used the actor model in the development of its Asynchronous Agents Library.[25] There are numerous other Actor libraries listed in the Actor Libraries and Frameworks section below.

## Current issues

According to Hewitt [2006], the Actor model addresses issues in computer and communications architecture, concurrent programming languages, and Web Services including the following:

• scalability: the challenge of scaling up concurrency both locally and nonlocally.
• transparency: bridging the chasm between local and nonlocal concurrency. Transparency is currently a controversial issue. Some researchers[who?] have advocated a strict separation between local concurrency using concurrent programming languages (e.g., Java and C#) from nonlocal concurrency using SOAP for Web services. Strict separation produces a lack of transparency that causes problems when it is desirable/necessary to change between local and nonlocal access to Web Services (see distributed computing).
• inconsistency: Inconsistency is the norm because all very large knowledge systems about human information system interactions are inconsistent. This inconsistency extends to the documentation and specifications of very large systems (e.g., Microsoft Windows software, etc.), which are internally inconsistent.

Many of the ideas introduced in the actor model are now also finding application in multi-agent systems for these same reasons [Hewitt 2006b 2007b]. The key difference is that agent systems (in most definitions) impose extra constraints upon the Actors, typically requiring that they make use of commitments and goals.

The actor model is also being applied to client cloud computing.[26]

## Programming with Actors

A number of different programming languages employ the actor model or some variation of it. These languages include:

### Actor libraries and frameworks

Actor libraries or frameworks have also been implemented to permit actor-style programming in languages that don't have actors built-in. Among these frameworks are:

Name Status Latest release License Languages
Actix Active 2018-01-23 MIT Rust
Aojet Active 2016-10-17 MIT Swift
Actor Active 2013-05-31 MIT Java
Vert.x Active 2017-06-21 Apache 2.0 Java, Groovy, Javascript, Ruby, Scala, Kotlin, Ceylon
Actor Framework Active 2013-11-13 Apache 2.0 .NET
Akka (toolkit) Active 2017-12-08 Apache 2.0 Java and Scala
Akka.NET Active 2017-01-22 Apache 2.0 .NET
Remact.Net Active 2016-06-26 MIT .NET, Javascript
Ateji PX Active  ?  ? Java
czmq Active 2016-11-10 MPL-2 C
F# MailboxProcessor Active same as F# (built-in core library) Apache License F#
Korus Active 2010-02-04 GPL 3 Java
Kilim[44] Active 2011-10-13[45] MIT Java
ActorFoundry (based on Kilim) Inactive 2008-12-28  ? Java
ActorKit Active 2011-09-13[46] BSD Objective-C
CloudI Active 2015-12-24[48] MIT C/C++, Elixir/Erlang/LFE, Go, Haskell, Java, Javascript, OCaml, Perl, PHP, Python, Ruby
Clutter Active 2016-03-21[49] LGPL 2.1 C, C++ (cluttermm), Python (pyclutter), Perl (perl-Clutter)
NAct Inactive 2012-02-28 LGPL 3.0 .NET
Retlang Inactive 2011-05-18[50] New BSD .NET
JActor Inactive 2013-01-22 LGPL Java
Jetlang Active 2013-05-30[51] New BSD Java
GPars Active 2014-05-09[52] Apache 2.0 Groovy
OOSMOS Active 2016-02-17[53] GPL 2.0 and commercial (dual licensing) C. C++ friendly
Panini Active 2014-05-22 MPL 1.1 Programming Language by itself
PARLEY Active? 2007-22-07 GPL 2.1 Python
Peernetic Active 2007-06-29 LGPL 3.0 Java
PostSharp Active 2014-09-24 Commercial / Freemium .NET
Pulsar Active 2016-07-09[54] New BSD Python
Pulsar Active 2016-02-18[55] LGPL/Eclipse Clojure
Pykka Active 2015-07-20[56] Apache 2.0 Python
Termite Scheme Active? 2009-05-21 LGPL Scheme (Gambit implementation)
Theron Active 2014-01-18[57] MIT[58] C++
Thespian Active 2016-02-11 GoDaddy Public Release[59] Python
Quasar Active 2016-01-18[60] LGPL/Eclipse Java
Libactor Active? 2009 GPL 2.0 C
Actor-CPP Active 2012-03-10[61] GPL 2.0 C++
S4 Inactive 2012-07-31[62] Apache 2.0 Java
C++ Actor Framework (CAF) Active 2017-01-10[63] Boost Software License 1.0 and BSD 3-Clause C++11
Celluloid Active 2016-01-19[64] MIT Ruby
LabVIEW Actor Framework Active 2012-03-01[65] National Instruments SLA LabVIEW
LabVIEW Messenger Library Active 2016-06-01 BSD LabVIEW
Orbit Active 2017-05-31[66] New BSD Java
QP frameworks for real-time embedded systems Active 2015-09-29[67] GPL 2.0 and commercial (dual licensing) C and C++
libprocess Active 2013-06-19 Apache 2.0 C++
SObjectizer Active 2018-02-07 New BSD C++11
Orleans Active 2017-03-27[68] MIT License C#/.NET
Skynet Active 2016-07-11 MIT License C/Lua
Reactors.IO Active 2016-06-14 BSD License Java/Scala
libagents Active 2016-07-18 Free software license C++11
protoactor Active 2017-05-01 Free software license Go/C#/python/js/java

Please note that not all frameworks and libraries are listed here.

## References

1. ^ Carl Hewitt; Peter Bishop; Richard Steiger (1973). "A Universal Modular Actor Formalism for Artificial Intelligence". IJCAI.
2. ^ a b c d William Clinger (June 1981). "Foundations of Actor Semantics". Mathematics Doctoral Dissertation. MIT.
3. ^ a b Irene Greif (August 1975). "Semantics of Communicating Parallel Processes". EECS Doctoral Dissertation. MIT.
4. ^ a b Henry Baker; Carl Hewitt (August 1977). "Laws for Communicating Parallel Processes". IFIP.
5. ^ "Laws for Communicating Parallel Processes" (PDF). 10 May 1977.
6. ^ a b c Gul Agha (1986). "Actors: A Model of Concurrent Computation in Distributed Systems". Doctoral Dissertation. MIT Press.
7. ^ "Home". Osl.cs.uiuc.edu. Archived from the original on 2013-02-22. Retrieved 2012-12-02.
8. ^ Carl Hewitt. Viewing Control Structures as Patterns of Passing Messages Journal of Artificial Intelligence. June 1977.
9. ^ a b Gul Agha; Ian Mason; Scott Smith; Carolyn Talcott (January 1993). "A Foundation for Actor Computation". Journal of Functional Programming.
10. ^ Carl Hewitt (2006-04-27). "What is Commitment? Physical, Organizational, and Social" (PDF). COIN@AAMAS.
11. ^ Mauro Gaspari; Gianluigi Zavattaro (May 1997). "An Algebra of Actors". Technical Report UBLCS-97-4. University of Bologna.
12. ^ M. Gaspari; G. Zavattaro (1999). "An Algebra of Actors". Formal Methods for Open Object Based Systems.
13. ^ Gul Agha; Prasanna Thati (2004). "An Algebraic Theory of Actors and Its Application to a Simple Object-Based Language" (PDF). From OO to FM (Dahl Festschrift) LNCS 2635.
14. ^ John Darlington; Y. K. Guo (1994). "Formalizing Actors in Linear Logic". International Conference on Object-Oriented Information Systems.
15. ^ Brinch-Hansen, Per (2002). The Origins of Concurrent Programming: From Semaphores to Remote Procedure Calls. Springer. ISBN 978-0-387-95401-1.
16. ^ Per Brinch Hansen, Monitors and Concurrent Pascal: A Personal History, Comm. ACM 1996, pp 121-172
17. ^ C.A.R. Hoare, Monitors: An Operating System Structuring Concept, Comm. ACM Vol. 17, No. 10. October 1974, pp. 549-557
18. ^ Brinch Hansen, P., Operating System Principles, Prentice-Hall, July 1973.
19. ^ a b Carl Hewitt, "What is computation? Actor Model versus Turing's Model", A Computable Universe: Understanding Computation & Exploring Nature as Computation. Dedicated to the memory of Alan M. Turing on the 100th anniversary of his birth. Edited by Hector Zenil. World Scientific Publishing Company. 2012
20. ^
21. ^ Robin Milner. Processes: A Mathematical Model of Computing Agents in Logic Colloquium 1973.
22. ^ C.A.R. Hoare. Communicating sequential processes CACM. August 1978.
23. ^ "Elements of interaction". Dl.acm.org. doi:10.1145/151233.151240. Retrieved 2012-12-02.
24. ^ "How Twitter Is Scaling « Waiming Mok's Blog". Waimingmok.wordpress.com. 2009-06-27. Retrieved 2012-12-02.
25. ^ "Actor-Based Programming with the Asynchronous Agents Library" MSDN September 2010.
26. ^ Carl Hewitt (September–October 2008). "ORGs for Scalable, Robust, Privacy-Friendly Client Cloud Computing". IEEE Internet Computing. 12 (5).
27. ^ Henry Lieberman (June 1981). "A Preview of Act 1" (PDF). MIT AI memo 625.
28. ^ Henry Lieberman (June 1981). "Thinking About Lots of Things at Once without Getting Confused: Parallelism in Act 1" (PDF). MIT AI memo 626.
29. ^ Jean-Pierre Briot. Acttalk: A framework for object-oriented concurrent programming-design and experience 2nd France-Japan workshop. 1999.
30. ^ Ken Kahn. A Computational Theory of Animation MIT EECS Doctoral Dissertation. August 1979.
31. ^ William Athas and Nanette Boden Cantor: An Actor Programming System for Scientific Computing in Proceedings of the NSF Workshop on Object-Based Concurrent Programming. 1988. Special Issue of SIGPLAN Notices.
32. ^ Darrell Woelk. Developing InfoSleuth Agents Using Rosette: An Actor Based Language Proceedings of the CIKM '95 Workshop on Intelligent Information Agents. 1995.
33. ^ Dedecker J., Van Cutsem T., Mostinckx S., D'Hondt T., De Meuter W. Ambient-oriented Programming in AmbientTalk. In “Proceedings of the 20th European Conference on Object-Oriented Programming (ECOOP), Dave Thomas (Ed.), Lecture Notes in Computer Science Vol. 4067, pp. 230-254, Springer-Verlag.”, 2006
34. ^ Darryl K. Taft (2009-04-17). "Microsoft Cooking Up New Parallel Programming Language". Eweek.com. Retrieved 2012-12-02.
35. ^ "Humus". Dalnefre.com. Retrieved 2012-12-02.
36. ^ Brandauer, Stephan; et al. (2015). "Parallel objects for multicores: A glimpse at the parallel language encore". Formal Methods for Multicore Programming. Springer International Publishing: 1–56.
37. ^
38. ^ "Deny capabilities for safe, fast actors". by Sylvan Clebsch, Sophia Drossopoulou, Sebastian Blessing, Andy McNeil
39. ^
40. ^
41. ^ Carlos Varela and Gul Agha (2001). "Programming Dynamically Reconfigurable Open Systems with SALSA". ACM SIGPLAN Notices. OOPSLA'2001 Intriguing Technology Track Proceedings. 36.
42. ^ Philipp Haller and Martin Odersky (September 2006). "Event-Based Programming without Inversion of Control" (PDF). Proc. JMLC 2006.
43. ^ Philipp Haller and Martin Odersky (January 2007). "Actors that Unify Threads and Events" (PDF). Technical report LAMP 2007.
44. ^ Srinivasan, Sriram; Alan Mycroft (2008). "Kilim: Isolation-Typed Actors for Java" (PDF). European Conference on Object Oriented Programming ECOOP 2008. Cyprus. Retrieved 2016-02-25.
45. ^ "Commit History · kilim/kilim · GitHub". Github.com. Retrieved 2016-02-25.
46. ^ "Commit History · stevedekorte/ActorKit · GitHub". Github.com. Retrieved 2016-02-25.
47. ^ "Commit History · haskell-distributed/distributed-process · GitHub". Github.com. Retrieved 2012-12-02.
48. ^ "Commit History · CloudI/CloudI · GitHub". Github.com. Retrieved 2016-02-25.
49. ^ "Git repository". Git.GNOME.org.
50. ^ "Changes - retlang - Message based concurrency in .NET - Google Project Hosting". Code.google.com. Retrieved 2016-02-25.
51. ^ "jetlang-0.2.9-bin.zip - jetlang - jetlang-0.2.9-bin.zip - Message based concurrency for Java - Google Project Hosting". Code.google.com. 2012-02-14. Retrieved 2016-02-25.
52. ^ "GPars Releases". GitHub. Retrieved 2016-02-25.
53. ^ "OOSMOS Version History". OOSMOS. Retrieved 2016-02-25.
54. ^ "Pulsar Design and Actors". Archived from the original on 2015-07-04.
55. ^ "Pulsar documentation". Archived from the original on 2013-07-26.
56. ^ "Changes — Pykka 1.2.1 documentation". pykka.org. Retrieved 2016-02-25.
57. ^ "Theron - Version 6.00.02 released". Theron-library.com. Retrieved 2016-02-25.
58. ^ "Theron". Theron-library.com. Retrieved 2016-02-25.
59. ^ "Thespian Releases". godaddy.com. Retrieved 2016-02-25.
60. ^
61. ^ "Changes - actor-cpp - An implementation of the actor model for C++ - Google Project Hosting". Code.google.com. Retrieved 2012-12-02.
62. ^ "Commit History · s4/s4 · Apache". apache.org. Retrieved 2016-01-16.
63. ^ "Tags · actor-framework/actor-framework · GitHub". Github.com. Retrieved 2016-02-25.
64. ^ "celluloid | RubyGems.org | your community gem host". RubyGems.org. Retrieved 2016-02-25.
65. ^ "Community: Actor Framework, LV 2011 revision (version 3.0.7)". Decibel.ni.com. Retrieved 2016-02-25.
66. ^ "Orbit release". GitHub. Retrieved 2017-05-31.
67. ^ "QP Active Object Frameworks - Browse Files at". Sourceforge.net. Retrieved 2016-02-25.
68. ^ "Orleans releases". GitHub. Retrieved 2016-06-08.