-
Notifications
You must be signed in to change notification settings - Fork 60
Peer
We call a peer any program that is connected to the bus, a peer is identified by a unique identifier called a PeerId that looks like this: MyAmazingPeer.0 (we use the <ServiceType>.<InstanceNumber> convention to identify different instances of the same service).
The PeerId of a peer is what identifies it on the Bus. It is possible to stop a peer then start it from another machine with the same PeerId without causing any problem (see Persistence for details on this). Starting a peer with a PeerId that is already in use on the Bus is not permitted, the Directory will refuse your registration on the Bus.
It is possible to set a PeerId to ServiceType.*, this will be understood by the Bus and replaced by ServiceType.<Guid>. This feature is mainly used by peers that are not persistent and don't need to be recognized from one run to the other (see Persistence for more details).