Why I love The Actor Model
What is the Actor Model?
The Actor Model is a mathematical theory that treats “Actors” as the universal primitives of digital computation. ~ Carl Hewit
In simpler terms it is an conceptual programming model that deals with concurrency.
The actor model is a computational paradigm that is based on the idea that everything in a system is an actor. An actor is basically an entity that has a state and defined behavior. Actors communicate with each other by sending and receiving messages.

The actor model is a very simple concept. It is also a very powerful concept. But it has some conceptual loopholes.
The Actor
An actor is basically an entity that has its own state and behavior. The state of an actor is its private data. The behavior of an actor is its public interface. Actors communicate with each other by sending and receiving messages.
By defination, it is the fundamental unit of computation. It embodies three main things:
- Computation: It has to do something.
- Storage: It has to store something.
- Communication: It has to communicate with something.

Some Loopholes:
One ant is no ant ~ Eo Willson
There cannot be one actor, they come in systems. They have addresses by which they can communicate with other actors.
Actor Axioms
- Crate more actors.
- Send messages to actors.
- Decide what to do with next message.
An actor cannot change or directly affect another actor. It can never exchange state with another actor.
But actors communicate with each other by sending and receiving messages. These messages are sent asynchronously. This means that the sender of a message does not have to wait for the receiver to process the message before it can continue, this greatly reduces the wait-time lag.
Conceptually only 1 message at 1 time is processed.
Why Actor Model
- It is a very simple concept.
- It actor model is a natural way to model concurrent systems.
- It actor model can be used to build scalable systems.
- It actor model can be used to build fault-tolerant systems.
LET IT CRASH
The Actor Model follows the "Let It Crash" idea. Each actor works alone, so if one fails, it doesn't affect the others. Supervisors watch over groups of actors, and when one fails, the supervisor can fix it. This makes the system stronger and able to recover from problems on its own.
Wrapping Up
The Actor Model is a great way to build concurrent programs.
It's like a group of people working on a project, each doing their own part. They talk to each other by sending messages, and if one person makes a mistake, it doesn't ruin the whole project.

Imagine if you and your hackathon team could work the same way! Instead of dealing with merge conflicts and endless arguments, ya'll could have been actors all along.