| || |
Single Shared ORM or Multiple Shared ORM
We have 2 suite of products.
Suite 1 - Intranet based products. For this automation efforts are already in progress and we have one single OR (~ORM).
Suite 2 - Internet (web) based products. For this I am assigned to begin the automation efforts. I am suppose to inherit the key-word driven methodology applied for suite 1.
I am having double thoughts of using same ORM and instead prefer to have another ORM that has objects for web based products. Reason to have another ORM is to have refined structure and keep Intranet & Internet separate.
I will appreciate if anyone else has more valid reasons to have separate paths for Internet & Intranet applications.
Re: Single Shared ORM or Multiple Shared ORM
Will appreciate if someone can guide me in right direction.....any similar threads....