Location Store — where who-is-where is written down

each process writes its own address, and another process reads it to connect

Location Store — where who-is-where is written down each process writes its own address, and another process reads it to connect server node · writes its own address · Architecture component server node writes its own address server node · writes its own address · Architecture component server node writes its own address Location Store · an external store such as Redis · Architecture component Location Store an external store such as Redis calling node · reads the address and connects · Architecture component calling node reads the address and connects register look up

Why no address goes into a configuration file

  • • Each process writes its address and the names it serves into the Store at startup, and refreshes that record while it lives. The record disappears when it stops.
  • • The caller reads the Store to find where to connect. Adding servers or restarting one at a different address changes nothing on the calling side.
  • • Which node a Spot or Actor is on right now is recorded here too. A Store is required in order to use Spots and Actors.