Is there also a place for dynamic routing using service Registry?
Can you compare these routing approaches? With WebSphere Fabric we do store the routing policies in the registry and as a consequence, there is a place for dynamic routing support with registries. We need however to differentiate where the routing decision takes place from where the policy is stored. Usually the endpoints and policies from the registry are cached in the ESB performing the routing, while usually caching efficiency patterns and the routing evaluation is performed in the bus on the fly, and not in the registry which would require a remote interaction. Efficient content-based routing leads to first a mapping of the context and the content to an agreed structure with semantics usually accessible with a SBVR-like human readable language (http://www.omg.org/spec/SBVR/1.0/). The performance implications of doing such content or context analysis require a local processing with an in-memory resolution of the policies or rules. You can see in the following real policy example tha
