As a migrant, I want my MigrantHub information to be continuously updating the feature that creates my service recommendations, so that I always get the most up-to-date and accurate suggestions.
Dev Info:
Essentially automatically running microservice #1 with a cron job to continuously and automatically update the information and export a new model every "x" units of time, to later be used by microservice #2.
Story Points: 2
Priority: Low
Risk: Low
Tasks:
[x] Research and try different ways of implementing this. Different solutions found:
[x] Creating another microservice as a cron job and deploying it (2hr)
[x] Moving ms#1 to GCP App Engine and using their Cron Job service with a cron.yaml (2hr)
[x] Use GCP's cloud scheduler to call ms#1's external HTTP URL (1hr)
[x] Implement the chosen solution and test (0.5hr)
[x] Write Demo Steps
[x] Get Customer Sign Off
***The chosen solution does not have any code to merge since we finally used GCP's cloud scheduler to implement this cron job, and it does not need any code.
***The update period chosen was once a day. ie. the sheet that the recommendation engine reads from will be updated every 24 hours.
As a migrant, I want my MigrantHub information to be continuously updating the feature that creates my service recommendations, so that I always get the most up-to-date and accurate suggestions.
Dev Info: Essentially automatically running microservice #1 with a cron job to continuously and automatically update the information and export a new model every "x" units of time, to later be used by microservice #2.
Story Points: 2 Priority: Low Risk: Low
Tasks:
cron.yaml(2hr)***The chosen solution does not have any code to merge since we finally used GCP's cloud scheduler to implement this cron job, and it does not need any code.
***The update period chosen was once a day. ie. the sheet that the recommendation engine reads from will be updated every 24 hours.
Demo Steps: No user demo steps.
Mockups: No mockups available.