Fetching new apis from APIM core do via database call or REST api? I think, we have to think about time to fetch all apis and starting time of a node. If num of apis increases, the startup time of a node may increase. This may critical for a containerized environments. We found some production instances which has around 1000 apis.
On Wed, Apr 26, 2017 at 1:56 PM, Sanjeewa Malalgoda <[email protected]> wrote: > In fully automated containerized environment can we assume we can see node > restarts. As i understood nodes come and go(each time we require we start > new instance and when its not in use it will terminate). In such scenario > having durable subscription or persisting data to local node do not make > much difference. > > But if we are thinking of traditional deployment then we may be able to > restart instances and reuse them. > @Lakmal, Pubudu any thoughts? > > Thanks, > sanjeewa. > > On Wed, Apr 26, 2017 at 11:34 AM, Pubudu Gunatilaka <[email protected]> > wrote: > >> On Wed, Apr 26, 2017 at 11:02 AM, Lakmal Warusawithana <[email protected]> >> wrote: >> >>> >>> >>> On Wed, Apr 26, 2017 at 10:51 AM, Manoj Gunawardena <[email protected]> >>> wrote: >>> >>>> Are we going to use durable subscription here? When ever gw node down >>>> and re start, >>>> it should fetch messages which add to the topic during the down time. >>>> In case durable subscription what is the mechanism to create client id >>>> for each gw.Is that discussed and confirm? >>>> >>> >>> No, we are not going to use durable topic. New gateways (scaling) or if >>> we restart a gateway, existing APIs will fetch via API Manager core. Only >>> new API (after boot up) notifications are getting via the topic and actual >>> API will fetch from the core. ( we can try what sanjeewa mention - getting >>> API from the topic - but previous APIs need to fetch from the core) >>> >>> >> >> When we restart a gateway node, it would be better to fetch only the >> updated APIs as well as the new APIs. Restarted gateway has the already >> fetched APIs and it is not worth to fetch all the APIs again. We will have >> to use durable subscription for this. >> >> If we consider the container scenario, are we persisting gateway >> artifacts? If we are not persisting gateway artifacts and restart the >> gateway container, then we need to fetch all the APIs from the core. IMHO >> it would better to persist data and load that data at restart as it would >> take time to fetch all the APIs from the core. >> >> 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 >> >> > > > -- > > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94713068779 <+94%2071%20306%208779> > > <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda. > blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/> > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Manoj Gunawardena Tech Lead WSO2, Inc.: http://wso2.com lean.enterprise.middleware Mobile : +94 77 2291643
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
