Replies: 1 comment
-
I'm not super familiar with this framework. The only pro I see in this framework is using lock-free MPSC instead of channels for the actor's communications. It makes communicating a way more performant. I already have a task in my roadmap to implement communication the same way in the future. The cons - it doesn't provide a native way for interop with Erlang/Elixir cluster, it doesn't have a Proxy feature. I also don't see anything like Monitor/Link features. It doesn't check the incarnation of the process. I haven't found a way how to make sync requests. I should also mention that they use GRPC, which is a pro for some cases but could be a con for others. Anyway, it's a good framework. I suppose I miss something and would appreciate it if anyone else could make a way more expressive comparison. |
Beta Was this translation helpful? Give feedback.
-
How does ergo compare to this similar library in terms of performance and developer experience?
https://proto.actor/
https://github.com/asynkron/protoactor-go#why-actors
Beta Was this translation helpful? Give feedback.
All reactions