Hi community,
At the moment we have a cyclic reference between two modules mentioned by Architecture Dashboard. We are not sure what is the best way to solve this problem. So I hope one of you can guide us in the right direction. In the image below you see a overview of the current situation.
In BrandCoreRange entity we store products that exist in the range of the brand or a division and in Product entity we store products with product information.
Perhaps we have placed the BrandCoreRange entity incorrectly? How do you guys think of this? If more information is needed to provide a good answer, please let me know!
Thanks,
Bart
Hi Bart
The best way to solve cyclic reference is
Hi Prathoswar,
Thanks for your answer and systematic approach :-)
I also think the 3rd point you mention is the best one in this scenario. If i may ask, where would you place this BL module, since I have two applications (Product Core Services and Brand Core Services)? Personally, I think I should create a third application that sits above these two concepts. Do you agree?
Yes, that will work. You can create a new core application above these two applications and place the BL module there.
Also, you can create a BL module in any one of the applications as that will also help and may avoid creating a new application. It seems both are core applications so no conflict will raise.
Now you can take decisions accordingly as you can create a new application or create a BL module inside any one application.
Thank you