Home/ Questions/Q 3352906
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T02:05:12+00:00

While designing (and then implementing) a layered application: Is it correct to use the

  • 0

While designing (and then implementing) a layered application:

Is it correct to use the same ORM objects accross all layers? (which would go against encapsulation).

Or the presentation, business and data layer should each have their own objects? (which would lead to lots of code repetition).

e.g. (just to illustrate the question): if one uses Linq to SQL in the Data Layer and Visual Studio’s O/R designer to generate the ORM objects, are those objects supposed to be used in the Business and Presentation Layers as well.

i.e.: Are the objects associated with the entities that the application handles a crosscutting issue?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It depends by your business. if you are talking about a small application you could do it.
    Usually the best practices wants to don’t expose the entity from the DAL to the presentation because doing that the layer are going to be tightly coupled and you could expose data that doesn’t make sense at the top layer (presentation)
    on the other hand you shouldn’t create a bunch of object per each layer.
    it’s always hard answer this question because it really depends by your needs.
    you can have a look at this book just to have an idea about

    http://books.google.co.uk/books?id=FyWZt5DdvFkC&printsec=frontcover&dq=martin+fowler+enterprise+architecture&source=bl&ots=eEEx4ATr5C&sig=sSmDmffOSALWfFZEaPyhkwwEq_I&hl=en&ei=SJnSTMuSJIHm4AaK9tW5Dw&sa=X&oi=book_result&ct=result&resnum=6&ved=0CDAQ6AEwBQ#v=onepage&q&f=false

    • 0