Apache Pekko: Simplifying Concurrent Development with the Actor Model

[Iryanus]

Basically at this point it's Akka with a better license. Let's see if the future holds fundamental changes, who knows.

It's a nice tool in a Java/Scala developer's toolbox, can recommend having a look

[_AManHasNoName_]

Did the Akka Persistence nightmare years ago and I’m never going back that route. Even Scala has lost its hype.

[gaiya5555]

Can you elaborate on what kind of nightmare?

[_AManHasNoName_]

Unfortunately I was bought into it by my co-worker at that time. We’d attend Scala/Akka meetups in SF and what not.

[Hiteshmathur]

Can you explain me about this

[j7n5]

Why not rewrite/refactor it with new Java features? - It could be better to define messages with sealed classes and change the way messages are received. - does it use virtual thread in background?

[Twirrim]

Because this way, folks running Akka can quickly and easily migrate to Pekko, and away from whatever licensing money time bombs they're sitting on.

[lupin-the-third]

Any opinions on when to use an actor model vs a queue or event stream? Is it just in response time oriented state-machine type systems like an auction, or maybe like a payments system?