[FOLIO-2010] Alternative Scheduling Approaches Created: 10/May/19 Updated: 25/Jan/23 Resolved: 25/Jan/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Marc Johnson | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | potential-decision | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||
| Description |
|
Context Following the conversations on
It could be useful to discuss those reservations and any alternative proposals (like use of the vert.x periodic API) to decide if we want to invest in those as well. Scheduling Needs (taken from
I believe any alternative approach needs to also fulfil the needs described to frame the current Okapi development. Initial Requirements
These closely mimic the current scheduling implementation in RAML Module Builder. The main differences are that it is tenant aware (rather than running as soon as the module is deployed) and limited to running on only a single instance. Possible Future Extensions
1) I've used the term task to be consistent with other parts of this issue |