Geek Answers Handbook

What are the signs of too much assembly separation?

While you often do not need one monolithic assembly for something more than a small project, it is possible to separate too much.

What are the signs / smells of too many sections?

+3
source share
4 answers

First (obvious): in a solution with a large number of projects, assemblies with only small (say 3-4) classes in them (assembly with only interfaces can be an exception).

Other: if an assembly somewhere in the middle layer of your project needs to import a ton of other assemblies in order to do its job.

+1
source

/, : , / .

+1

circular dependencies are a dead sacrifice; -)

+1
source

By clicking in the other direction, you may have too little separation of the assembly if there is a whole bunch of unrelated things in one assembly.

An approach that seemed useful to me was to support functional subsystems in discrete assemblies. Some of these subsystems can be huge - and some of them can be quite small.

0
source

More articles:


All Articles