L3 - Default Context:
In the Optimize back-end, we have a typical layer structure that every code goes through if a request is filed against the back-end: Rest -> Service -> Reader/Writer
Right now, all branch analysis service layer logic, like authorization checks, are part of the reader layer. We should add a service layer to separate the two concerns.
AT:
- there is a branch analysis service layer
Hint:
Since you already touch the branch analysis: It could also make sense to rename all occurrences of "correlation" to branch analysis. The naming is sometimes inconsistent and the correlation naming is back from the old days.