Hi Nuwan/Joe, On Thu, Jan 12, 2017 at 5:49 PM, Joseph Fonseka <[email protected]> wrote:
> > > On Thu, Jan 12, 2017 at 5:12 PM, Nuwan Dias <[email protected]> wrote: > >> >>> Gateways can receive subscription data in 2 ways. >>> >>> 1) Load all subscription data at server startup >>> >>> For this, APIM Core component will have a service to return all >>> subscriptions of all APIs. >>> >> >> I think this API should accept the number of Subs to load on startup. In >> the initial version we will support 0 and all only. 0 being the default >> (which means we load Subs on demand). Moving forward we can enhance this by >> using different policies such as 'most recent', 'most used', etc. >> > +1. I'll write it that way. > >>> 2) Load subscription data on-demand depending on the API requests it >>> receives. >>> >>> For this, APIM Core component will have a service to return >>> subscriptions of a given API. >>> >> > Are we going to create a new service for above ? As an alternative we can > consider using Store REST API to fetch the subscription details. Advantages > include one less API to maintain, it is already protected with OAuth and it > has/can support above cases. > @Joe: Initially I also was thinking to use the store API. But later decided to have a new one due to following reasons. 1. Store API's getSubsubscriptions() results does not contain key information. To have key information, we need an extra table join wth key mapping table. 2. We already have an REST API for admin services which is used for internal usage (i.e. server to server). So this service seems more suitable to be there. 3. If we have a separate service for internal usage, we can change it anytime without breaking external systems. If we use the store API itself, we won't have that freedom. Thanks, Bhathiya > > Thanks > Jo > > > > > >> >>> In either case, gateways store received subscription data in an >>> in-memory data structure. Therefore, gateways should receive subscription >>> updates (new subscriptions/unsubscribe notifications etc.) too. We are >>> planning to do this using a JMS topic. (This will not be limited to JMS and >>> will be configurable later.) When there are any updates to subscriptions, >>> APIM Core component will add that information to a topic, to which gateways >>> are subscribed to. Then gateways can update their subscription data which >>> they have stored in memory. >>> >>> Then we will have a handler at the gateway (most probably the Key >>> validation handler itself) to use stored subscription data to validate >>> subscriptions of incoming requests. >>> >>> >>> Note: The subscription data received by the gateway from APIM core will >>> contain certain API and Application related information as well. The reason >>> is that we have decided to generate JWT tokens at gateway nodes. So we need >>> those data to include in the JWT. >>> >>> Thanks, >>> -- >>> *Bhathiya Jayasekara* >>> *Senior Software Engineer,* >>> *WSO2 inc., http://wso2.com <http://wso2.com>* >>> >>> *Phone: +94715478185 <+94%2071%20547%208185>* >>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj >>> <http://www.linkedin.com/in/bhathiyaj>* >>> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* >>> *Blog: http://movingaheadblog.blogspot.com >>> <http://movingaheadblog.blogspot.com/>* >>> >> >> >> >> -- >> Nuwan Dias >> >> Software Architect - WSO2, Inc. http://wso2.com >> email : [email protected] >> Phone : +94 777 775 729 <+94%2077%20777%205729> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > -- > *Joseph Fonseka* > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 772 512 430 > skype: jpfonseka > > * <http://lk.linkedin.com/in/rumeshbandara>* > > -- *Bhathiya Jayasekara* *Senior Software Engineer,* *WSO2 inc., http://wso2.com <http://wso2.com>* *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj <http://www.linkedin.com/in/bhathiyaj>* *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* *Blog: http://movingaheadblog.blogspot.com <http://movingaheadblog.blogspot.com/>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
