Instance Matching for Subscriber Name Mapping
The FTL server's instance matching algorithm determines the mapping from subscriber names to durables.
Instance Matching describes the matching algorithm that the FTL server uses to select an application instance, and so determine the implementation of endpoint publisher and subscriber objects using transport connectors.
After a first pass determines those transport connections, a second pass uses the identical matching algorithm to determine a mapping from subscriber names to durables.
Because the two passes are independent, you can configure the subscriber name mapping independently from instance connections in separate application instance definitions. For example, you could key transport connections to the host, and key the subscriber name mapping to the identifier.
You can use this independence to reduce the number of application instance definitions.