Closed garethjevans closed 4 years ago
Great proposal 👍 👍
Recommend looking at the architecture design first before refactoring or you may end up with a different shaped legacy problem. Versioning is critical to this sort of loose-coupling so this needs to consider https://github.com/jenkins-x/enhancements/issues/24 at the design stage.
Recommend looking at the architecture design first before refactoring or you may end up with a different shaped legacy problem. Versioning is critical to this sort of loose-coupling so this needs to consider #24 at the design stage.
@tdcox absolutely! This is the first of a number of proposals that we're expecting to produce to help get us to where we need to be. Ensuring these changes fit within the overall JX strategy is key - otherwise... what's the point!
It would be awesome to consider publishing architectural diagrams that describe the current state of things but also incorporate our longer-term ambitions with regards to decomposition. The most useful diagram type might bethe "physical model" as described here ( https://en.wikipedia.org/wiki/4%2B1_architectural_view_model ) but it shouldn't diminish the value of the other perspectives.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan
in a comment when ready.
The full list of commands accepted by this bot can be found here.
A proposal to start to decompose JX into a number of modules to make it more extensible.