Timeline for Scheduled Task in webservice
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2021 at 18:23 | comment | added | Hans-Martin Mosner | My first idea is to update the next wakeup time by the scheduler when it puts the task into the worker queue, not by the worker when it has performed the task. But this indeed something that should be tuned using actual experience. | |
| Oct 20, 2021 at 11:07 | comment | added | shoaib30 | To the last point, if I do not update the table on execution, how will the scheduler know when to run it next as the time to run is not the same for every user.? | |
| Oct 20, 2021 at 11:05 | comment | added | shoaib30 | this is how Celery works and it does a good job. The single scheduler thread would a single point of failure and bottle neck, which is okay for now. I just need to be aware of it. | |
| Oct 20, 2021 at 10:59 | comment | added | shoaib30 |
This helps, currently the work itself is being doing by different microservices which I can call workers in your terminology. I am calling REST API to trigger it, instead you are suggesting I can pass it as a message on a queue which would make it a lot better without network overhead.
|
|
| Oct 20, 2021 at 10:34 | history | answered | Hans-Martin Mosner | CC BY-SA 4.0 |