4 ms·

besides Ray, are there other tools or platforms that embrace the agent actor architecture model?

by skadamat 3y ago

felixgallo 3y ago
https://www.erlang.org/ https://www.erlang.org/ https://elixir-lang.org/ https://elixir-lang.org/
- photonthug 3y ago
  Elixir is amazing, see also stuff like https://github.com/bitwalker/libcluster https://github.com/bitwalker/libcluster . I'm always surprised there's not more excitement generated by the possibility of having language-level features that would normally require all the weight of something like k8s. I don't get the impression that many people are seriously using it for data-engineering work though, which seems like a shame
- Nezteb 3y ago
  Elixir definitely! If you need to use Go, there is also ergo: https://github.com/ergo-services/ergo https://github.com/ergo-services/ergo Yet another cool tool is lunatic: https://github.com/lunatic-solutions/lunatic https://github.com/lunatic-solutions/lunatic
Sardtok 3y ago
Akka uses the actor model. https://doc.akka.io/docs/akka/current/typed/actors.html https://doc.akka.io/docs/akka/current/typed/actors.html IIRC, Akka based their implementation on Erlang (possibly OTP), but it's been a long time since I did anything with either Erlang or Scala, and I never used Akka in Java.
- stereosky 3y ago
  Akka was indeed inspired by Erlang. For a modern take, there's Apache Pekko (incubating), a fork of Akka 2.6.x https://github.com/apache/incubator-pekko https://github.com/apache/incubator-pekko
jgraettinger1 3y ago
Estuary Flow derivations [1], I suspect (I work here)? You write a program which has messages pushed to it, which maintains and updates an internal state, and which publishes output messages. You can build cyclic data-flows [2] - not just DAGs - which seems a key ingredient. You can also write contract-based tests that verify the end-to-end behaviors of your "agents" [3]. Today, you're limited to SQLite or TypeScript. Looking forward, we aim to open it up to any program packaged in a docker container. [1] https://docs.estuary.dev/concepts/derivations/ https://docs.estuary.dev/concepts/derivations/ [2] https://docs.estuary.dev/concepts/derivations/#approving-transfers https://docs.estuary.dev/concepts/derivations/#approving-tra... [3] https://docs.estuary.dev/concepts/tests/ https://docs.estuary.dev/concepts/tests/
brahbrah 3y ago
Dask added an actor model after seeing it in Ray. I’ve used dasks in some computationally intensive applications (already had existing dask infrastructure which is why we didn’t go with rays)

besides Ray, are there other tools or platforms that embrace the agent actor architecture model?

felixgallo 3y ago

https://www.erlang.org/ https://www.erlang.org/ https://elixir-lang.org/ https://elixir-lang.org/

photonthug 3y ago
Elixir is amazing, see also stuff like https://github.com/bitwalker/libcluster https://github.com/bitwalker/libcluster . I'm always surprised there's not more excitement generated by the possibility of having language-level features that would normally require all the weight of something like k8s. I don't get the impression that many people are seriously using it for data-engineering work though, which seems like a shame
Nezteb 3y ago
Elixir definitely! If you need to use Go, there is also ergo: https://github.com/ergo-services/ergo https://github.com/ergo-services/ergo Yet another cool tool is lunatic: https://github.com/lunatic-solutions/lunatic https://github.com/lunatic-solutions/lunatic

Sardtok 3y ago

Akka uses the actor model. https://doc.akka.io/docs/akka/current/typed/actors.html https://doc.akka.io/docs/akka/current/typed/actors.html IIRC, Akka based their implementation on Erlang (possibly OTP), but it's been a long time since I did anything with either Erlang or Scala, and I never used Akka in Java.

stereosky 3y ago
Akka was indeed inspired by Erlang. For a modern take, there's Apache Pekko (incubating), a fork of Akka 2.6.x https://github.com/apache/incubator-pekko https://github.com/apache/incubator-pekko

jgraettinger1 3y ago

Estuary Flow derivations [1], I suspect (I work here)? You write a program which has messages pushed to it, which maintains and updates an internal state, and which publishes output messages. You can build cyclic data-flows [2] - not just DAGs - which seems a key ingredient. You can also write contract-based tests that verify the end-to-end behaviors of your "agents" [3]. Today, you're limited to SQLite or TypeScript. Looking forward, we aim to open it up to any program packaged in a docker container. [1] https://docs.estuary.dev/concepts/derivations/ https://docs.estuary.dev/concepts/derivations/ [2] https://docs.estuary.dev/concepts/derivations/#approving-transfers https://docs.estuary.dev/concepts/derivations/#approving-tra... [3] https://docs.estuary.dev/concepts/tests/ https://docs.estuary.dev/concepts/tests/

brahbrah 3y ago

Dask added an actor model after seeing it in Ray. I’ve used dasks in some computationally intensive applications (already had existing dask infrastructure which is why we didn’t go with rays)