Akka Typed: Stateful and Stateless Actors | Rock the JVM 

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

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

myHappiness += 100

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

Thank you Daniel, really nice explained

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

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

Great !! very useful for PR :)

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.

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

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?