If you have an _IS module and a _CS module and then your app. If the Structure is the same that you use in the IS module as what you want to use in the _CS and app itself, is it best practice to consume that structure straight from the _IS module from the app or is it better to create a duplicate of that structure in the _CS module and then consume it from there since the app is not meant to consume from _IS directly in general? Structures create soft links, which also makes it less clear on the best way.
On the one hand, I don't want to create duplicate structures as that means more maintenance. But on the other hand, if one day the _IS structure changes in a way that I don't want pulling through into the app then a duplicate that now becomes not identical might be beneficial.Thoughts?
Hello Nicholas.
In general, it is best to keep the modules as separate and modular as possible, so that they can be easily maintained and updated independently. However, if there is a need for the CS module to access data or functionality provided by the IS module, it is appropriate for it to consume that structure.
However, I think that the best solution would be to add a Sync module to your app that can consume from both CS and IS, and also keeping your Sync logic in its own module helps to troubleshoot and maintain your code.
Hope it helps!
Paulo Rosário
Hi,
You can use it... Side references in Core layer is allowed.
Hi @Nicholas Campbell were you able to find a correct answer to your question. Im also trying to figure out same thing. To me as well consuming a structure directly from an _IS module to another module other than its _cs module doesn’t feel right.