Re: [Architecture] Retrieving Rating value of API in the GET_API resource API

+1 to Option 1, an APIs ratings are not something that everyone will be interested in. Those who want that data can make the additional API call to retrieve it. On 6 March 2017 at 13:40, Chamalee De Silva wrote: > Hi Dilan, > > I agree with your point in terms of performance point of view. > But

Re: [Architecture] Retrieving Rating value of API in the GET_API resource API

Hi Dilan, I agree with your point in terms of performance point of view. But when thinking of implementing the retrieval of Rating value of an API in terms of re-usability in scenarios like API composition which we are going to implement in the future I think it is fair to have this as a separate

Re: [Architecture] Retrieving Rating value of API in the GET_API resource API

Hi Chamalee, I think that the 1st option would be the slowest in performance as it requires two network calls to APIs + two separate DB Calls to get all information related to an API. So, IMO, we should rather focus on other two options which only require one network call, instead of the first.

Re: [Architecture] Retrieving Rating value of API in the GET_API resource API

Thanks all for the responses. I will go ahead with option 1. So with that, - The rating value of the API *will not be returned* in the response of the getAPI resource API. - Separate resource APIs will be implemented to do the following. - add rating val

Re: [Architecture] Retrieving Rating value of API in the GET_API resource API

Hi Chamalee, The response in [1] suggests option 1 in general. It explains few good points that are worth looking at. Furthermore, in addition to Chamin's response, getAPI call looks

Re: [Architecture] Retrieving Rating value of API in the GET_API resource API

On Wed, Mar 1, 2017 at 1:45 PM, Chamalee De Silva wrote: > Hi all, > > I am working on adding REST APIs for the following operations. > > 1. Rate an API (add rating) > 2. Get rating of an API (given the UUID of the API) > > > A separate table is going to be added to store for API_RATINGS like wha