LearnViz CompSci
Home / Learn / Concurrency & Parallelism / Actor Model

Intermediate Topic 23 of 51 Concurrency & Parallelism

Actor Model

Isolated entities communicating by messages.

How it works

In the actor model, the basic unit of computation is an actor: an independent entity with private state that communicates only by sending asynchronous messages to other actors' mailboxes. In response to a message, an actor can update its state, create new actors and send messages. Because state is never shared and each actor processes one message at a time, there are no data races within actors. Supervision hierarchies handle failures with a let-it-crash philosophy. Frameworks include Erlang and Elixir's OTP, Akka and Orleans.

Where it is used

Telecom switches, chat and messaging back ends, IoT platforms, game servers and fault-tolerant distributed systems use actors, and location transparency lets actors span machines.

Common pitfall

Message ordering is only guaranteed between pairs, and unbounded mailboxes can fill under load. Request-response needs correlation and timeouts, and deadlocks can still occur through waiting cycles. Debugging asynchronous flows is hard. Large messages are expensive to copy. Design actors with clear responsibilities, bound mailboxes and add monitoring and supervision strategies.

Where it fits in the course

Actor Model is topic 23 of 51 in Concurrency & Parallelism, rated Intermediate. It follows Green Threads. The next topic is Communicating Sequential Processes.

Practice and explore

How to study this topic

  1. Read the explanation above and restate the definition in your own words.
  2. Open the interactive lesson and answer its mini quiz.
  3. Read the common pitfall, then write a short example that avoids it.
  4. Check your understanding in the Concurrency & Parallelism quiz, and revisit the topic if you miss a question.

Frequently asked questions

What is Actor Model?
Isolated entities communicating by messages. It belongs to Concurrency & Parallelism and is an intermediate-level topic.
Where do people use Actor Model?
Telecom switches, chat and messaging back ends, IoT platforms, game servers and fault-tolerant distributed systems use actors, and location transparency lets actors span machines.
What is the most common mistake with Actor Model?
Message ordering is only guaranteed between pairs, and unbounded mailboxes can fill under load.
What should I learn before this topic?
Start with Green Threads, the topic just before it in Concurrency & Parallelism.
How can I practice it?
Answer the mini quiz in the interactive lesson, then take the Concurrency & Parallelism quiz.
Is Actor Model hard to learn?
It is an Intermediate topic. Be comfortable with the Beginner topics in this area first, then read the common pitfall carefully, since it is where most mistakes happen.
How long does it take to learn Actor Model?
Most learners can read the explanation and finish the interactive lesson in under an hour. Fluency comes from applying the idea, so plan a few short practice sessions with the quiz.
Which topics are related to Actor Model?
Green Threads, Communicating Sequential Processes, Futures and Promises Model are closely connected. The full list is in the related topics section of this page.
What should I study after Actor Model?
Continue with Communicating Sequential Processes, the next topic in Concurrency & Parallelism.

Related topics