Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use _akka-cluster_ and _akka-cluster-sharding_ #84

Open
SebastianSchmidl opened this issue Jun 11, 2018 · 0 comments
Open

Use _akka-cluster_ and _akka-cluster-sharding_ #84

SebastianSchmidl opened this issue Jun 11, 2018 · 0 comments
Labels
Nice-To-Have On Hold Work on this issue or pull request is on hold question Further information is requested

Comments

@SebastianSchmidl
Copy link
Owner

Issue

Currently all actors are spawned in the same JVM. We should use akka-cluster to distribute the actors across multiple nodes/JVMs. Cluster sharding allows distributing actors across nodes of an akka cluster without knowing their physical location.

This will need an application.conf file for configuring remoting, seed nodes, persistance provider, ....

Keywords:

  • actor migration (persistent actors need a distributed journal, state can be replayed, non-persistent actors lose their state)
  • cluster, cluster roles
  • shards, ShardCoordinator
  • remoting

Problem Description

All state is hold in-memory and there is currently only one JVM in use. State of ADBMS Dactors will potentially get to big to fit into memory of one node (JVM).

Supporting Information

@SebastianSchmidl SebastianSchmidl added question Further information is requested On Hold Work on this issue or pull request is on hold Nice-To-Have labels Jun 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice-To-Have On Hold Work on this issue or pull request is on hold question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant