Following the context of the definitions Motoko abstracts the complexity of the Internet Computer with a well known, higher-level abstraction: the actor model. Each canister is represented as a typed actor. …its messages are processed one-at-a-time, even when issued in parallel by concurrent ac…

As nomeata pointed out, there are multiple layers at play here. On one level, we have a simple form of actor (mapping to IC canisters). An actor communicates by message passing as you would expect, messages are received atomically, they can send an arbitrary number of follow-up messages without blo…

Actor Model fundamentals compromised?

Developers Language Support

nerdoutcj May 17, 2021, 12:13am 5

Agree. The question is not Async vs. Atomicity. Rather, why the fundamental feature of Actor Model that makes it so beautiful - one does not have to synchronize anything between the communications - is not preserved. Is it by design? Is it interim?

Topic		Replies	Views
How does Motoko deal with reentrancy? Education	1	1033	September 1, 2020
I have several questions around the actor model, data structures and the functional programming aspects of the IC Developers	7	981	March 8, 2022
Improvement proposals for Motoko Developers Functional-Programming	14	848	November 20, 2021
Feature Request (Motoko): Extend or import functionality into actor classes Language Support Motoko	3	746	October 11, 2022
Motoko Documentation Motoko Documentation	1	1119	June 7, 2023

Actor Model fundamentals compromised?

Related topics