Hi All,
I watched a video on prioritising architecture violations recently.
Top of the list was:
Upper and side violations to orchestrators - followed by
Upper and side violations to end users.
Not sure if the video is out of date? Do we still have orchestrators? Wasn't this an additional layer on the canvas which we no longer have. I'm not 100% sure on this.
Also, how can an upper violation exist on something like an end user or orchestrator when its the top of the hierarchy? If there is an upper violation in this example would it be referring to say, something in the core which is accessing it? But then wouldn't that show up in the discovery tool in the core module and not the end user module? Or would it show up in both modules? e.g. You would see an upward red arrow in both modules in the discovery tool (the core and the end user module).
Thanks
Hi JayPea,
You are correct. With the introduction of weak references in OutSystems 11, the 4-layer canvas become a 3-layer canvas (foundation layer, core layer and end-user layer), with the orchestration being removed.
Upper violation would be a foundation module consuming a core or end-user module or a core module consuming an end-user module.
Discovery asset recent versions should already be taking the 3-layer canvas into account.
Kind Regards,João
Thank you.
So in the discovery tool would an upper validation be illustrated the red up arrow and would this arrow appear in both the end user module and the core or foundation modules that are affected. Or would the arrow simply appear in the core or foundation module?
From my experience, it would just appear as a red arrow on the lower module with an upward reference.
That's what I thought, which leads me to my next question.
How would you identify Upper and Side violations in end user modules in order to priorities them?
I advise you to go through the Architecting Sustainable Applications guided path, especially the Validating an Architecture (explaining how to use Discovery and Architecture Dashboard to assess the architecture status of an application and discover findings) and the Refactoring Applications (explains how to prioritise the findings and how to solve them strategically, together with its pitfalls) courses.
They explain better than I would :)
Thanks, this is what has led to the questions. :o)
I think I have enough clarity for now.
Still. Not removed from the guided path.