locked
Design solution RRS feed

  • Question

  • User-1011572351 posted

    is better to have a single project to my entity, or have multiple modules by separating them?

    myproject.entities => all entitys separating by folder..

    or

    myproject.moduleCustomer 

    myproject.moduleFinancial

    ...

    ?

    OBS: I use asp.net mvc and separete my entitys

    Monday, September 30, 2013 4:49 PM

Answers

  • User-821857111 posted

    is better to have a single project to my entity, or have multiple modules by separating them?

    Unless there is a compelling reason to do otherwise, it is usual to keep your domain objects in one project. If you want to categorise them by folder, that's up to you. But you may find some entities are slightly more tricky to categorise, and then you forget which folder they are in and have to go hunting for them 3 or 6 months down the line...

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, October 1, 2013 12:38 AM
  • User-488622176 posted

    It is better to load 1 assembly then to load 10. The loading of assemblies does have a performance impact that is unrelated to the size of the assembly. But this is also not to be exagerated

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 2, 2013 8:08 AM

All replies

  • User-821857111 posted

    is better to have a single project to my entity, or have multiple modules by separating them?

    Unless there is a compelling reason to do otherwise, it is usual to keep your domain objects in one project. If you want to categorise them by folder, that's up to you. But you may find some entities are slightly more tricky to categorise, and then you forget which folder they are in and have to go hunting for them 3 or 6 months down the line...

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, October 1, 2013 12:38 AM
  • User-1011572351 posted

    have a big project with several entities not give performance problem? being that it would be a separate dll less to load into memory

    Tuesday, October 1, 2013 7:48 AM
  • User-821857111 posted

    If you get performance problems from loading tiny dlls into memory, your issues lie elsewhere and cannot be solved through code.

    Tuesday, October 1, 2013 7:53 AM
  • User-1011572351 posted

    one big assembly loading best that various assembly?

    Tuesday, October 1, 2013 11:21 AM
  • User-821857111 posted

    Your domain objects library is never likely to reach an equivalent size of, say, System.Web.dll which is loaded up every time your application starts - that just over 5MB, by the way.

    Tuesday, October 1, 2013 3:44 PM
  • User-488622176 posted

    It is better to load 1 assembly then to load 10. The loading of assemblies does have a performance impact that is unrelated to the size of the assembly. But this is also not to be exagerated

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 2, 2013 8:08 AM