c# – In an architecture, does the number of DLLs influence performance? Scalability?


I usually create my solution like this:

Entity – Class Library (Classes, entities)

Utils – Class Library (Classes of help, security, generate xml, in short, functions of all kinds)

Repository – Repository class ( repository patterns)

Map – Class Libary – ORM Mapping Classes, be it Nhibernate or Entity using Fluent API

Test – Test

Web Project – Here my web project, if I want to separate in "module" I use the areas. (Modules = Financial, Inventory, Billing, etc.)

I use this structure regardless of the size of the project, whether small or giant

My question is: In an architecture, does the number of dll's influence performance? scalability? Leaving it like this would be bad if my project grew?

Or it would be better to create a class library for each module (a class library for a finance module, another for billing, and so on. Just like a web project, a web project for finance, billing, etc.).

Links about architecture are welcome.


The only problem with multiple DLLs is a slight increase in time when starting the application, as all DLLs will be located and their dependencies resolved, but this impact on performance is not worth worrying about.

Scroll to Top