Hi, So every time an app is accessed the incremented counter needs to be written to db. Isn't it an considerable overhead if apps are accessed frequently. How about keeping the counter in a cache or write to db say for every 10 times(a meaningful value) an app is accessed?
Touched, not typed. Erroneous words are a feature, not a typo. On Nov 14, 2014 5:20 PM, "Lahiru Cooray" <[email protected]> wrote: > Hi all, > > I'm trying to add a new feature to AppManager to unable user to *sort* > the subscribed Apps by accessed frequency. > > In the back end there will be a counter used to store the no of hits per > App against each subscriber. When a subscriber access an App (via > AppManager gateway end point URL) the counter will be increased. > > [image: Inline image 3] > > > And in the front end there will be two options that user the can select. > (recently added Apps/ most frequently accessed Apps) > > *Proposed table structure:* > > *CREATE TABLE APPMGR_APP_HIT_TOTAL* > *(* > *API_ID INT(10) NOT NULL,* > *USER_ID VARCHAR(50) NOT NULL,* > *HIT_COUNT BIGINT,* > *PRIMARY KEY (API_ID,USER_ID)* > *)* > > Highly Appreciate your feedbacks. > > -- > *Lahiru Cooray* > Software Engineer > WSO2, Inc.;http://wso2.com/ > lean.enterprise.middleware > > Mobile: +94 715 654154 > > _______________________________________________ > 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
