Computing/calculating/planning a dinner happens in the main REST backend. This is a service which could very good be separated into an own microservice. This would enable scaling up this part onto many machines.
[x] define a slim request data model which only contains data needed for calculation (team UUIDs, latitude/longitude location, diet, ...?)
[x] define a slim response data model which only contains data needed for saving the plan (and maybe some additional information about the calculation metadata might be nice, e.g. duration of the calculation (or some better indicator for compution time), timestamps, ...)
[x] separate service into own microservice
[x] remove the stuff we do not need anymore in the main backend
[x] add microservice to docker-compose.yml
[ ] would be nice if it works with heroku
[ ] Amazon Lambda support? (split into own issue)
[ ] OpenFAAS support? (split into own issue, if it does not come for free anyways with Micronaut Functions)
Computing/calculating/planning a dinner happens in the main REST backend. This is a service which could very good be separated into an own microservice. This would enable scaling up this part onto many machines.
[x] define a slim request data model which only contains data needed for calculation (team UUIDs, latitude/longitude location, diet, ...?)
[x] define a slim response data model which only contains data needed for saving the plan (and maybe some additional information about the calculation metadata might be nice, e.g. duration of the calculation (or some better indicator for compution time), timestamps, ...)
[x] separate service into own microservice
[x] remove the stuff we do not need anymore in the main backend
[x] add microservice to docker-compose.yml
[ ] would be nice if it works with heroku
[ ] Amazon Lambda support? (split into own issue)
[ ] OpenFAAS support? (split into own issue, if it does not come for free anyways with Micronaut Functions)