@Abhimaran In latest APIM 3.0.0 milestone release, we are using eager loading to deploy the APIs. Basically, when the gateway server starts up, gateway system services retrieve relevant APIs (published with the gateway's label) from APIM core REST API and they will be deployed into gateway runtime.
IMO, we should enable eager loading as the default behavior. It is true that we need to minimize the startup time of the server. But from the gateway user's perspective, in a default gateway profile, the response time of the initial request is much important than the server startup time. Further, the decision of enabling eager loading and lazy loading depends on the number of APIs deployed in the gateway (If we have a few APIs, there won't be an impact on the server startup time by having eager loading, but if the number of APIs is a huge amount, eager loading won't work we should enable lazy loading). Thus I think the default config should go with eager loading since the default gateway profile is not suppose to be flooded with a huge amount of APIs. On Tue, Oct 31, 2017 at 3:00 PM, Prasanna Dangalla <[email protected]> wrote: > > On Tue, Oct 31, 2017 at 11:18 AM, Chamin Dias <[email protected]> wrote: > >> Hi, >> >> What would be the default behavior after this implementation? In other >> words, what would be the best way out of the below 2 options? >> >> 1. By default, only lazy loading is enabled. Users can disable that (lazy >> loading) and enable eager loading if needed. >> 2. By default, only eager loading is enabled. Users can disable that >> (eager loading) and enable lazy loading if needed. >> > > IMO when we are deciding the default value we should forcus on the > performance of the server loading time. WDYT ? > >> >> Thanks. >> >> On Mon, Oct 30, 2017 at 5:42 PM, Sanjeewa Malalgoda <[email protected]> >> wrote: >> >>> As per most recent requirements we saw, we might need to support both >>> lazy loading and eager loading. >>> There can be situations where first response time matters(but server >>> loading time does not matter). Also there can be situations server loading >>> time matters but first response time does not matter. >>> Better to have both IMO. >>> >>> Thanks, >>> sanjeewa. >>> >>> On Tue, Feb 7, 2017 at 9:58 AM, Ishara Cooray <[email protected]> wrote: >>> >>>> Hi Isuru, >>>> >>>> The plan is to provide a configuration that allows one to load all the >>>> apis as well at the server start up or load the api artifact as the gateway >>>> receives first api call. That can be decided according to the requirement. >>>> . >>>> >>>> Thanks & Regards, >>>> Ishara Cooray >>>> Senior Software Engineer >>>> Mobile : +9477 262 9512 <077%20262%209512> >>>> WSO2, Inc. | http://wso2.com/ >>>> Lean . Enterprise . Middleware >>>> >>>> On Mon, Feb 6, 2017 at 7:02 AM, Isuru Haththotuwa <[email protected]> >>>> wrote: >>>> >>>>> Hi Ishara, >>>>> >>>>> After the summary is loaded at server startup, are we loading the rest >>>>> of information as well? If so, how does that happen? >>>>> >>>>> On Mon, Jan 30, 2017 at 2:06 PM, Ishara Cooray <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am working on $Subject and following is the use case and the >>>>>> approach we are going to address. >>>>>> >>>>>> *Motivation:* >>>>>> In order to reduce the server startup time we thought of not loading >>>>>> the apis at the server startup. >>>>>> Then we need a way to validate api requests to avoid DOS attacks such >>>>>> as api requests with invalid context, passing to the api core level. >>>>>> >>>>>> *Solution:* >>>>>> Therefore we are planing to load summary of all apis(name, context, >>>>>> uriTemplates) into memory at server startup so that when an api request >>>>>> comes to the gateway it will first validate the availability of that >>>>>> api/resource. >>>>>> >>>>>> To get the api summary info there will be Rest Service in APIM core. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> For newly added apis we can update the in memory cache via a JMS >>>>>> Topic (later we can support for other message brokers as well) . >>>>>> >>>>>> >>>>>> >>>>>> Following components will be written to address these scenarios. >>>>>> >>>>>> >>>>>> 1. REST Service to retrieve API summary - *API Core* >>>>>> 2. APISummaryLoader to load APIsSummary at server startup - *GW* >>>>>> 3. JMS Topic receiver - *Core* >>>>>> 4. JSM topic listener - *GW* >>>>>> 5. APIContextValidationHandler - *GW* >>>>>> >>>>>> >>>>>> Thanks & Regards, >>>>>> Ishara Cooray >>>>>> Senior Software Engineer >>>>>> Mobile : +9477 262 9512 <+94%2077%20262%209512> >>>>>> WSO2, Inc. | http://wso2.com/ >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks and Regards, >>>>> >>>>> Isuru H. >>>>> +94 716 358 048 <+94%2071%20635%208048>* <http://wso2.com/>* >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> -- >> Chamin Dias >> Mobile : 0716097455 >> Email : [email protected] >> LinkedIn : https://www.linkedin.com/in/chamindias >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thilini Shanika Senior Software Engineer WSO2, Inc.; http://wso2.com 20, Palmgrove Avenue, Colombo 3 E-mail: [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
