Actor system for the JVM developed by Electronic Arts
1–10 of 95 posts
Re: Actor system for the JVM developed by Electronic Arts
#2Does anyone know how it compares to Akka?
Re: Actor system for the JVM developed by Electronic Arts
#3> Orbit is a framework to write distributed systems using virtual actors on the JVM. A virtual actor is an object that interacts with the world using asynchronous messages.
Could anybody elaborate on this? How does an actor differ from an object that uses promises to talk to a server?
Re: Actor system for the JVM developed by Electronic Arts
#4It looks interesting, but seems to be dead.
The repository has virtually no activity since september 2020.
Re: Actor system for the JVM developed by Electronic Arts
#5> Orbit is a framework to write distributed systems using virtual actors on the JVM. A virtual actor is an object that interacts with the world using asynchronous messages. Could anybody elaborate on this? How does an actor differ from an object that uses promises to talk to a server?
Yip, that's basically just an actor.
When people talk about actor-based languages or frameworks however, theyre suggesting syntax primitives which help express this more naturally.
The simple pitch is: OO where objects could be on any machine.
Re: Actor system for the JVM developed by Electronic Arts
#6> Orbit is a framework to write distributed systems using virtual actors on the JVM. A virtual actor is an object that interacts with the world using asynchronous messages. Could anybody elaborate on this? How does an actor differ from an object that uses promises to talk to a server?
Objects, actors, and (micro-)services are basically the exact same concept at different scales.
Re: Actor system for the JVM developed by Electronic Arts
#7> Orbit is a framework to write distributed systems using virtual actors on the JVM. A virtual actor is an object that interacts with the world using asynchronous messages. Could anybody elaborate on this? How does an actor differ from an object that uses promises to talk to a server?
actor model has nothing to do with promises
Re: Actor system for the JVM developed by Electronic Arts
#8> Orbit is a framework to write distributed systems using virtual actors on the JVM. A virtual actor is an object that interacts with the world using asynchronous messages. Could anybody elaborate on this? How does an actor differ from an object that uses promises to talk to a server?
Usually the difference is the "mailbox" an actor has, making the difference more about the level you're calling an actor more than the differences in any code you might write.
Re: Actor system for the JVM developed by Electronic Arts
#9> Orbit is a framework to write distributed systems using virtual actors on the JVM. A virtual actor is an object that interacts with the world using asynchronous messages. Could anybody elaborate on this? How does an actor differ from an object that uses promises to talk to a server?
It’s not the same as async objects. There are differences between different score systems. But have a look at Elang and Akka for example.
But I’m actor systems the actors maybe more stateful that you typical object and be location transparent. Communication between actors does require knowledge of if another actor is in process or remote.
Also the actor supervising model is a completely different way of recovering from errors than in OO systems.
Re: Actor system for the JVM developed by Electronic Arts
#10“Exactly one” is a hard concept to get right. How do they ensure that exactly one instance of an actor is alive at once, without sacrificing latency of actor start and/or while tolerating network partitions?