Hi, Please find the answers inline.
On Wed, Feb 8, 2017 at 12:43 PM, Lalaji Sureshika <[email protected]> wrote: > Hi Pubudu, > > In above diagram,both the gateway types are pointing to same > keymanager.,Have we considered the scenario of having different > keymanagers per each gateway node.For example,multiple DC > deployment[master-slave] scenario..Then how we will extend the UI > experience in Store side? > > We can have different key managers per gateway node which shares the same data source. But we cannot use multiple key managers which have different implementations. Store will work with the assigned key manager node and that will not break the UI experience as we share the same data source. @Roshan: When starting up the gateway node, we only provide the label for the gateway node. This could be a startup argument for the gateway node. In the database we will record the URL of the gateway node along the label name. That's how we map the gateway node with a label. @Harsha: There will be a default label which we provide. When an API is published, jms message will be published. If there are gateways up and running, they will receive the message. When a request comes to the gateway, it will request for the API by giving its label. Then the publisher will only provide the API, if only the API has the relevant label. Hope this is clear. Thank you! -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
