<p>I am looking for some introductions to the actor model. I don't mind books in specific programming languages, as long as they don't distract away or restrict the presentation of the model</p>
<p>Is this a good one?</p>
<blockquote>
<p>Actors: A Model of Concurrent Computation in Distributed Systems (MIT Press), by Gul Agha, 1986</p>
</blockquote>
<p>I am uncertain because</p>
<ul>
<li>it is a PhD dissertation which might be for things that were experimental and then found useless, and</li>
<li>it was in 1986 and I am not sure how much the model has changed.</li>
</ul>
<p>Thanks.</p>

CC BY-SA 4.0
2021-02-12T08:05:59.420Z
We will need to know who the target audience is. Yes you, so tell us a little about your self. What is you experience / level of education? What is your motivation for learning this?
ctrl-alt-delor
CC BY-SA 4.0
2021-02-12T11:49:49.440Z
kindergarten. interested.
Tim
CC BY-SA 4.0
2021-02-15T01:16:21.207Z
"Everything I needed to know, I Iearned in kindergarten." - Robert Fulghum. If only that were true of all of us.
Scott Rowe
CC BY-SA 4.0
2021-02-15T01:25:09.510Z
I don't see much when I search, except for references to my favorite missing in action person, Bret Victor. You could try this link as a starting point: [A World Without Agile, Can You Imagine?](https://hurlbert.medium.com/without-agile-where-would-you-go-11712c15403c). I am not sure of the need for concurrency in much mainstream development, but I suppose things could change. People could get sharper wits. ("The universe is full of magical things patiently waiting for our wits to grow sharper" - Eden Phillpotts)
Scott Rowe
CC BY-SA 4.0
2021-02-15T20:03:32.207Z
@ScottRowe what are needed in mainstream development?
Tim
CC BY-SA 4.0
2021-02-16T11:56:54.000Z
@Tim What I was thinking of is the large amount of basic data and forms programming, with just 'CRUD' data access (Create record, Read, Update, Delete). Object Oriented is not needed for that really, and concurrency certainly is not, beyond adding a timestamp to the Where clause. What is your interest in Actor? It was designed for systems where resources are being continually reused at high speed, like a telephone system. I created a multithreaded data server, but there was no contention, just separate requests, so not much need for concurrency. What would you like to find out?
Scott Rowe
<resource-request><textbook><concurrency>
introduction materials to the actor model?
# introduction materials to the actor model?

(Asked by: username_0 on 2021-02-11)

I am looking for some introductions to the actor model. I don't mind books in specific programming languages, as long as they don't distract away or restrict the presentation of the model

Is this a good one?

> Actors: A Model of Concurrent Computation in Distributed Systems (MIT Press), by Gul Agha, 1986

I am uncertain because

* it is a PhD dissertation which might be for things that were experimental and then found useless, and
* it was in 1986 and I am not sure how much the model has changed.

Thanks.

**Tags:** resource-request, textbook, concurrency

> **Comments:**
> **username_1**: We will need to know who the target audience is. Yes you, so tell us a little about your self. What is you experience / level of education? What is your motivation for learning this?  
> **username_0**: kindergarten. interested.  
> **username_2**: "Everything I needed to know, I Iearned in kindergarten." - Robert Fulghum. If only that were true of all of us.  
> **username_2**: I don't see much when I search, except for references to my favorite missing in action person, Bret Victor. You could try this link as a starting point: [A World Without Agile, Can You Imagine?](https://hurlbert.medium.com/without-agile-where-would-you-go-11712c15403c). I am not sure of the need for concurrency in much mainstream development, but I suppose things could change. People could get sharper wits. ("The universe is full of magical things patiently waiting for our wits to grow sharper" - Eden Phillpotts)  
> **username_0**: @ScottRowe what are needed in mainstream development?  
> **username_2**: @username_0 What I was thinking of is the large amount of basic data and forms programming, with just 'CRUD' data access (Create record, Read, Update, Delete). Object Oriented is not needed for that really, and concurrency certainly is not, beyond adding a timestamp to the Where clause. What is your interest in Actor? It was designed for systems where resources are being continually reused at high speed, like a telephone system. I created a multithreaded data server, but there was no contention, just separate requests, so not much need for concurrency. What would you like to find out?  

---

## 0 answers

