I faced the following picture where we have multiple modules and when I was asked about how many applications could be created, my solution wasn't the correct answer. If any of you guys could help me understanding how we should organize these modules into new applications according to the best practises I'd really appreciate.
Hi エドモッタ ,
You can categorize the applications as follows:
Application 1: End-User #1 only.
Application 2: End-User #2, includes Core C and Library C (This is a separate application because Core C and Library C are only used by End-User #2).
Application 3: Contains Core A, Library A, Core B and Library B (These are common core modules used by both End-User #1 and End-User #2).
Thanks,
Vipin Yadav
Hello,
This is how it should be
Application#1 - End User#1
Application#2 - End User#2, Core C, Library C
Application#3 - Core A, Library A, Core B, Library B
You can refer below document to better understand the answer. The document explains a similar scenario.
https://success.outsystems.com/documentation/best_practices/architecture/designing_the_architecture_of_your_outsystems_applications/application_composition/applying_the_architecture_canvas_to_applications/
Hope it helps!
Junaid
Hi,
Application1 : Enduser1
Application2: Enduser 2, Core C, Library c
Application3 : Core A, Library A, Core B, Library B
Can I know the reason for the dislike
Since the Library could be a common use in the future, we should have seperated apps for them
So in my opinion, it shoud be.
App 1: Core A, Core B
App 2: End User #2, Core C
App 3: End User #1
App 4: Lib A
App 5: Lib B
App 6: Lib C