Walaa wrote:
You'll need to explain, why did you think of the modules separation in Approach 1?
If there is no good reason for separation and/or if entities have relations accross such modules, or there might be transactions holding entities from more than module, then I'd go for the 2nd approach.
The thing is, it is more of a management and maintenance issue...I started looking at the first module and that module alone has +- 100 tables = +- 100 entities. The second module has almost another 100. and I still have several more modules to go. The overlap or shared entities maybe handle in a "share module" ?
