Petals ESB Container

The registry should be exploded in two parts

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 3.1
  • Fix Version/s: 5.0.0
  • Component/s: Registry
  • Security Level: Public
  • Description:
    Hide

    Currently the registry contains two kind of information:

    • information needed to route messages,
    • information about service contract.

    So the registry should be exploded in two parts to be optimized against each use cases:

    • retrieve service contracts. In this use case performances are not critical, the user should be able to get its WSDL under 1 second,
    • build the endpoints list against message content. Performance and content of this use case are critical,
    Show
    Currently the registry contains two kind of information:
    • information needed to route messages,
    • information about service contract.
    So the registry should be exploded in two parts to be optimized against each use cases:
    • retrieve service contracts. In this use case performances are not critical, the user should be able to get its WSDL under 1 second,
    • build the endpoints list against message content. Performance and content of this use case are critical,
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 15:25:18 +0200 - edited

This information has been taken into account writting the new Petals Registry based on Hazelcast, coming with Petals 5, we have:

  • a dedicated area to endpoint locations,
  • a dedicated area to endpoint description that is not accessed when routing message exchanges.
Show
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 15:25:18 +0200 - edited This information has been taken into account writting the new Petals Registry based on Hazelcast, coming with Petals 5, we have:
  • a dedicated area to endpoint locations,
  • a dedicated area to endpoint description that is not accessed when routing message exchanges.

People

Dates

  • Created:
    Thu, 9 Sep 2010 - 17:07:57 +0200
    Updated:
    Mon, 5 Oct 2015 - 15:26:49 +0200
    Resolved:
    Mon, 5 Oct 2015 - 15:25:18 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.