optimus
optimus copied to clipboard
Introduce Job Run/Job Scheduling bounded context
Description As part of this we will introduce a domain for dealing with jobs which are scheduled on are in running state.
Acceptance Criteria
- All the code related to job run will be in a separate domain
Out of Scope
- Handling of replay functionality in Optimus
Depends on : 575
Tech Details Technical details
- [ ] All api related to job run will be part of scheduling domain
- [ ] All service and handlers related to job run will be part of this domain
- [ ] Should consume the contracts defined by resource and job domain