Hello Outsystems-Community =)
i watched this video about Validating Apps Architecture.
At 2:55 they say that it's not a good idea to consume a functionality from another End-user App.
Not to have side references makes sense to me:
a) If both apps are just on development environment and I want to deploy the End-user App2 for the first time, i also have to deploy End-user App1 even it may be not ready for the first deployment right?
b) If i need to make a change(bugfix...) in an action in Core B which is consumed in End-user App2, i have to deploy both apps, even if there may be changes in End-user App1 which i don't want to deploy now.
At 3:20 the speaker of the video said, that it's now not possible to deploy End-user App 1 without End-user App2 in the deployment plan.
This confussed me a bit. Why couldn't I deploy App1 without App2?
If i haven't deployed App2 and I want to deploy App1 for the first time, I don't need to deploy App 2 as well, or do i have to?
If i do changes in Core B which are not consumed in App2, I could deploy without App2 in the deployment plan, couldn't I?
If i do changes in Core B which are consumed in App2, i would update App2 and add it to the deployment plan, because i want the newest version in staging or production.
Is there anything which I don't understand right?
I would be awesome if you could give me feedback.
Thank you very much in advance.
Hi,
According to above diagram, first time you can deploy End User App1 alone without End User App2. But if you want to deploy End User App 2 then also need to deploy End User App1.
regards
Your questions understanding are correct. However, while designing the architecture blue print at first place one should avoid having side references between two End user apps as it would unnecessary create dependency & would result in complex deployment process. If i do changes in Core B which are not consumed in App2, I could deploy without App2 in the deployment plan, couldn't I? - even if you could do that but that's not right at first place itself from architecture perspective(as the app grows you will see the problem), rather identify the common elements and place it in correct layer .For details you can got through these documents:https://success.outsystems.com/documentation/best_practices/architecture/designing_the_architecture_of_your_outsystems_applications/validating_your_application_architecture/ https://www.outsystems.com/blog/posts/application-architecture/