Actor Model Explained

Подписаться 352 тыс.

Просмотров 125 тыс.

50% 1

In this video, we are talking about the Actor Model. I hope you'll find it useful.
Also, please check the related blog post
finematics.com/...
Seven Concurrency Models in Seven Weeks ► amzn.to/37nDkBj (great book on different concurrency models including the Actor Model - affiliate link)
If you have more time please check this excellent video where Carl Hewitt talks more about the Actor Model
• Hewitt, Meijer and Szy...
Website ► finematics.com
Follow me on Twitter ► / finematics
Donations:
Bitcoin ► 18ngQa7qzfg9RpstBz3ZCSm2fAzm6tqaa4
Lightning ► tippin.me/@fin...
Referral links:
Brave Browser ► brave.com/fin661 (ads-free browsing)
Ledger Nano S ► shop.ledger.com?r=2af228941155 (hardware wallet for crypto)
If you like this video, give it a like, share it and subscribe to my channel.
Thanks for watching!

Опубликовано:

16 окт 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 87

@paullee2449 5 лет назад

Excellent explanation. Concise and unambiguous.

@dmytromelnychuk1909 6 лет назад

Thanks! High level model, short and informative. Such videos are the best!

@Kaslor1000 3 года назад

Not Elixir, but Erlang, give credit where credit is due.

@mmubeen1189 4 года назад

Perfect Level of information passed to understand the concept, Great Job :)

@Finematics 4 года назад

Thanks!

@mmubeen1189 4 года назад

@@Finematics It will be great if you also make a video on Spring framework. I'm waiting :)

@dmitrym3757 5 лет назад

Thanks a lot! Is there any chance to see a CSP explaination in near future?

@avimehenwal 3 года назад

I understood how CSP work in clojure through a rich hickey's video. He explains it like a CS god, in full glory

@dna1238 3 года назад

many thanks for posting this explanation .

@ShoaibKhanZ Год назад

This has to be the best explanation! Clear and concise!

@aammssaamm Год назад

Which means you do not get the concept either, cause he doesn’t.

@SunilPatil-hs8wd 3 года назад

Thanks Dude. Awesome video.

@MohamedAli-nr2dr 2 года назад

Magnificent explanation

@RajeshRai-dk7ed 2 года назад

perfect video to easily understand the actor model

@artyomkuznetsov8050 4 года назад

Hello. Your explanation is very good. Thanks!

@dansanger5340 4 года назад

What about Erlang? Is there some dispute that Erlang uses the Actor model?

@aDifferentJT 3 года назад

Elixir is built on BEAM, same as Erlang, they are fairly similar.

@davidshipman5964 16 часов назад

Elixir and Lisp Flavored Erlang are just different frontends for Erlang. They all use the actor model.

@CoolITTrends 3 года назад

Great job! Thanks mate!

@sapnokiranii 4 года назад

Great and clear explanation, thanks!

@APEF92 6 лет назад

Really informative, thanks¡

@Finematics 6 лет назад

Thank you!

@namooman6447 5 лет назад

Very well explained. Thanks

@prasanthmp500 3 года назад

why cant we use spring cloud technologies instead of Actor model ?

@billmoney1 3 года назад

Awesome vid

@strong1019 6 лет назад

Great explaining!

@Werna8Pumba 4 года назад

Great explanation :)

@kokizzu 5 лет назад

umm.. how actor model susceptible to deadlock?

@Guncraker 5 лет назад

Due to no usage of locks at all

@IvoYueh 5 лет назад

Although actors are asynchronous and don't have to wait for other actors, their state changes may rely on conditions from other actors. If there is a circular dependency between actors, then they can deadlock each other.

@lulu4882 4 года назад

how is code reuse usually implemented in the actor model?

@aammssaamm 4 года назад

By breaking it into a single responsibility functions.

@lulu4882 4 года назад

@@aammssaamm interesting, thanks. could you provide an example please?

@aammssaamm 4 года назад

@@lulu4882 Excuse me?

@lulu4882 4 года назад

@@aammssaamm an example of actors sharing a single responsibility function.

@JB-nw1ix 6 лет назад

Great video!

@lherfel 2 года назад

thanks

@MrErtghj23 5 лет назад

GOOD JOB!! ❤️💪🏻

@ishunyu 4 года назад

Sounds very similar to goroutines in terms of the theory. Anybody know the diff?

@sdwvit 4 года назад

also similar to javascript event loop

@sawthinkar 6 лет назад

Thanks for the video. Could you please set up BAT payment for your website, finematics, so that I can make contributions while learning stuff posted there?

@Finematics 5 лет назад

done, better late than never

@sadaneotmane1437 5 лет назад

Thanks !

@Ilyushya Год назад

You forgot about Erlang, GParS and Kotlin

@JK-sy4ym 6 лет назад

best explanation! really appreciate this.

@Finematics 6 лет назад

Thanks!

@bilelkhedira 5 лет назад

fantastic +1

@张小亮-j5k 5 лет назад

awsome~

@0xssff 4 года назад

thank you

@thechhavibansal 4 года назад

best🔥

@izzatzr 2 года назад

the term of mailbox is not a requirement for the actor model

@babafunmiseadebowale7746 Год назад

“two actors with the same identity can have different addresses” why do two actors have the identity?

@flogginga_dead_horse4022 4 года назад

seems a lot like how processes are implemented in Elixir, I could be wrong :P edit: oops I missed the ending

@masteryoda9044 Год назад

Actor models are good looking people who can act.

@piyushmajgawali1611 4 года назад

This is certainly what I don't need

@gSalomeV 5 лет назад

sweet

@Андрей-й2р2ъ 6 лет назад

Thanks for the video man. I found it really helpful for my friend with his course project so he doesn't need to read an akka book. 😁

@MilanVVVVV 5 лет назад

Tip: he probably should

@AdrianBoyko Год назад

It’s mind-boggling that people produce content about the actor model without mentioning the Pony programming language.

@hpal 4 года назад

this sounds like Abramov

@aammssaamm 4 года назад

There should be no actor's mailbox overflowing as there are not so many messages which can be sent to an actor. In any case the number of messages can be optimized by the system optimization.

@Finematics 4 года назад

Correct. The Actor Model can be susceptible to mailbox overflowing, but with a proper implementation this issue can be mitigated and never occur.

@aammssaamm 4 года назад

@@Finematics Sorry, you don't seem to understand the topic.

@Finematics 4 года назад

Interesting. I'm looking forward to your explanation of the topic.

@nickeldan 8 месяцев назад

So, Erlang.

@web3.yuanming Год назад

@coatiguriguazu 11 месяцев назад

The video would have been even nicer if the host wasn't chewing bubble gum

@cvetanvelikov2440 3 года назад

Thanks for the explanation but please do not chew gum while talking, it's disgusting

@aammssaamm 4 года назад

Message is not explained.

@Finematics 4 года назад

Hi Anne, in this context a message is just a simple piece of data (any data) that is usually send to a specific recipient.

@aammssaamm 4 года назад

@@Finematics But you don't understand how exactly it works.

@Finematics 4 года назад

Looking forward to your explanation what a message in the Actor Model is

@flogginga_dead_horse4022 4 года назад

Still looking forward to Anne's video :D

@aammssaamm 4 года назад

@@flogginga_dead_horse4022 Sorry, I do not work for free.

@bilelkhedira 5 лет назад

Thanks

@bobj8690 4 года назад

“two actors with the same identity can have different addresses” why do two actors have the identity?

@Fridrih123 4 года назад

Let's say, I have counter and a button. When I perss the button (one actor), I send message to counter (another actor) about this event. This two actors have different identities. If I add another button into UI, I'll have two actors with same identities (they're both buttons and respond to click), but they will have different internal state (hovered, pressed, idle) and different addresses. If we take implementation of this system in HTML, we will have two HTMLButtonElments (identity) inside our DOM tree (system) with different addresses (e.g position inside DOM tree)

@thisisnotajoke 3 года назад

@@Fridrih123 Aren't you mixing up identity with "type"? Two buttons on a page are both of type "" , but do not have the same identity. Of course with HTML it is somehow ambiguous what exactly "identity" means if no "id" attribute has been specified, but then I would argue that the address is actually part of the id (even everything else about both buttons is the same and they do not have an "id", then we can still identify them by their location in the tree). Now going back to the original comment, I too think that the sentence at hand was a bit confusing. A better wording would have been: "two (or more) addresses can point to the same actor".