System Architecture - Dependency limits?

System Architecture - Dependency limits?

  

Hi all,

Has anyone encountered any soft or hard dependency limits when creating systems? I'm trying to break our app down into reusable sections but I don't want to go too far and end up with a system that won't build because there's too many modules.

Cheers!

Not sure what you want to achieve, but are you really confident that you end up with, say, 256, reusable modules?

And i mean modules that are used by more than 3 applications?


In any case, it will build if you chop it up, but you do get a performance hit I think.



First off, thank you for the reply.

I don't think we're likely to hit that many but potentially 30 or 40 if all the interfaces we need aren't merged into larger modules. I'm just trying to make sure we start off on the right foot and don't regret going one way or the other from the start.