Petals Documentation > Petals ESB > Petals ESB 5.5.0 > Page Comparison - Petals ESB "Registry" (v.8 vs v.9)

Petals ESB "Registry"

Version 8 by Christophe DENEUX
on Jun 03, 2014 10:29.
<< Changes from 7 to 8
compared with
Version 9 by Victor NOËL
on Oct 15, 2015 15:39.
(show comment)
Changes from 9 to 10 >>
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View Page History
...
The Petals ESB "Registry" is an internal component storing internal data. The Petals ESB "Registry" can be view as a distributed in-memory database shared by all Petals ESB nodes of the Petals network.

For example, before to send a message to a service provider, the Petals ESB "Router" will request the Petals ESB "Regsitry" "Registry" to elect the right endpoint according to information of the message (interface name and/or service name and/or endpoint name).

Data stored in the registry are:
...
* topology.

{note}The implementation of Petals ESB "Registry" must be the same for all nodes of a sub domain.{note}

{column}
...

The Petals ESB "Registry" implementation selection process is:
# if an implementation is set in the topology definition ({{topology/domain/sub-domain/registry-implementation}}), it is used,
# otherwise, the implementation used is the one available in the Petals ESB classpath.

...