Akka Typed: Stateful and Stateless Actors | Rock the JVM

[@nimatrueway]

I love your tutorials! They are in perfect form. By the way, I can't wait to watch more of "Scala 3" series.

[@rockthejvm]

Will do more!

[@no_more_free_nicks]

Thanks that was a great introduction, I have a job interview where I have to create a simple service using actors.

[@aethermass]

Great intro to Behaviors with Akka Typed. I recommend doing a video with an example of an Akka Typed timer/scheduler. Cheers =)

[@rockthejvm]

Will do - lots more incoming!

[@vicc8881]

myHappiness += 100

[@Nick-mp4jl]

Thank you Daniel, really nice explained

[@rockthejvm]

Glad it helped!

[@GVLPedro]

Great !! very useful for PR :)

[@rockthejvm]

Glad it helps!

[@GVLPedro]

@@rockthejvm I would like a video showing the different types of ExecutionContext (scala.concurrent.ExecutionContext.Implicits.global) and when to use.

[@javierramosrodriguez5512]

Maybe it is just terminology, but for me both actors are stateful. They have internal state. One is mutable and another one is not.

[@rockthejvm]

Sure - as long as you got the idea, that's all I wanted

[@javierramosrodriguez5512]

@@rockthejvm yes, as always, this video was very helpful. Thank you!

[@christianvalverde1247]

There is something thats not clear to me. when using persistent typed actors, there is a trait EventSource which should not be extended wich is good for functional style actors .....all the samples use a singleton object ... what if i wanted to map each item in a warehouse to a persistent actor, then the problem is functional style forces me to use singleton objects ... so i cant find a way to use persistente actors in the scenario. ....... any clue would be appreciated.

[@rockthejvm]

Having each item with its own persistent actor might be too granular.

[@christianvalverde1247]

@@rockthejvm what should be the ideal case ?

[@rockthejvm]

@@christianvalverde1247 it depends on what items you hold and how you access them, but the "DAO" should be a persistent actor

[@prashantsable7982]

Great Video. Quick question - For some if I wanted to retry the message, How can we achieve it without waiting for the next message. i.e. If you just send "emotionalActorSystem ! EatChocolate" I wanted to execute it 2 times based on some condition without waiting for the next message. Can we do context.self ! EatChocolate

[@rockthejvm]

You can simply send the message twice, i.e. call `emotionalActorSystem ! EatChocolate` two times?

[@prashantkumar-hx1dv]

you an crate the actor using the actor system or by extending the actor trait

[@mangos1346]

akka-typed seems unnecessary complicated than akka-actor, and with constant creation of new object of behavior for every incoming message, it seems like a performance penalty. Why would we use akka-typed in the first place?

[@rockthejvm]

Boilerplate has nothing to do with performance. This code is what aesthetics sacrifice for type safety, which was one of the major flaws of "old" actors.