-
Feature
-
Resolution: Done
-
Normal
-
None
-
None
-
3
-
False
-
-
False
-
0% To Do, 0% In Progress, 100% Done
-
-
Feature Overview
This is Architectural runway aiming to stabilize and simplify the service.
Currently all the background processing is happening in goroutines spanned in place and all the control is on the database.
We want to implement easy background processing, that will help control the job processing for the component and will prepare for running the jobs in separate components in the future.
Background and Strategic Fit
We need to stabilize the service, figure out why it's so memory hungry and simplify debugging to get it to a maintainable state.
Goals
Improve maintainability of the service.
Requirements
requirement | Notes | Is Mvp? |
Predictable job procesing with flow control | Yes | |
Correlated logs from a single job and job types | Yes | |
Prepare for extracting jobs to worker component | No |
Non-Functional Requirements
The solution should be easy a quick to implement, we don't need a state machine.
Customer Information/Supportability
- Probably no, just implementation detail as support do not see logs.
- We might be able to show the Job id in the UI to simplify reporting cases.
Documentation Considerations
- None