Decide on the endpoints structure

[iwoork]

Here's my proposal for the endpoints:

Option 1: Separate a Report and Probability endpoints

• The Report endpoint will simply save self-reported information
• The Probability endpoint accepts self-reported symptoms as parameter and outputs a probability from data science

Option 2: Combine Report and Probability as one endpoint

• POSTing a data to /report will not only save the submitted report but will also send back a response which includes the probability

[rashnil-git]

Option 1 was what I had in my architecture diagram. I prefer one as it makes the api lightweight and asynchronous. Client can just push the data and api can work on storing that. Otherwise if there are DB related issues, it will delay the stats response as well. client can make asynchronous calls to api endpoints and get the results back from probability endpoint.

[rashnil-git]

Also it will allow us to have different configurations for different types of workload and use cases.

[iwoork]

Let's go for Option 1. I guess call it 'Assess' or 'Probability' makes more sense?

POST /assess

[rashnil-git]

How about:

Endpoint 1 for submission:

POST /survey

Endpoint 2 for probability:

POST /stats?

[iwoork]

Sounds good. Let's do that.

[rashnil-git]

I have added tickets in project board. I will have them ready by this weekend.

[rashnil-git]

End Points created.

/stats : https://github.com/findthecluster/api-app/issues/12

[rashnil-git]

/survey endpoint : https://github.com/findthecluster/api-app/issues/11

[rashnil-git]

Wiki Page : https://github.com/findthecluster/api-app/wiki