A brief introduction to the actor model & distributed actors

[@siyaram2855]

Please come back James! The world needs you. There is no one like you. People need to know about this, you are the only on who can pull this out. Please make more videos on Elixir/Phoenix. You can make subscription based screencast website.

[@rahulkulkarni1780]

Wonderful explanation! Pushing process/state to the end clients is an interesting idea! Looking forward to learn more about these ideas…

[@JGBSolutions]

Dude I knew you were going to mention Elixir and Erlang but your stuff is good. Really good. I subscribed.

[@branmuller]

This video is fantastic, underrated channel wow

[@MMABeijing]

first time viewer. liked the video, subbed to channel. Amazing explanation, what a teacher you are, and great visual as well. May I ask what tool you use to make that type of presentation?

[@linz4213]

Fantastic introducing important concept, not mentioning language superiority (OTP rocks BTW)

[@yehudamakarov]

lol this content is stellar well done

[@siyaram2855]

James, don't you think kubernetes solvs the same purpose? Why someone would learn erlang/elixir when you can fo sane things with Go and kubernetes?

[@ihsanpro9406]

This saves more cost and better concurrency because you can run millions of process within a single pod inside kubernetes

[@yaseengousesamudri9390]

At 2:54, processes are *NOT* light-weight when compared to threads, instead threads are lightweight when compared to processes. Actors are generally more light-weight when compared to threads though.

[@sprobertson]

I assume it was specifically about erlang/beam processes (a lot of what was said about processes only makes sense in that context)

[@yaseengousesamudri9390]

@@sprobertson yeah, it makes sense then

[@GubenkovED]

Wonderful presentation! Can you please share the tools you used for the animations?

[@ThislsYusuf]

This should be the template for tutorials.

[@bilelkhedira]

Wonderful

[@rishabh_gour]

2:54 - "processes are lightweight when compared to threads". Isn't it the otherway around?

[@JGBSolutions]

No, processes are indeed lightweight. The BEAM (elixir, erlang) controls them as far as I understood them.

[@Mekhami]

elixir processes, not system processes.

[@rishabh_gour]

@@Mekhami that makes sense now, thanks

[@knowthen]

I'm referring to processes in the actor model,. Are you thinking of system processes? I can see how that might be confusing.

[@Mekhami]

@@knowthen i don't particularly like how you're sort of implying the actor model is specific to the BEAM, when of course it isn't. This video seems to be more "actor model in the context of beam" than about the actor model specifically, which explains why, to me, it's missing some of the key concepts behind the actor model.

[@ximono]

Is the solution perhaps CRDT?