3 tier x 4 tier, using an ORM

[Bruce One]

My ORM is responsible to map my tables to data object classes, but then I
face a big quizz: should I work with only this tier, putting all my complex
algorithms in this same tier, or should I create another tier, above this
DataObj class, to handle more abstract methods (rather than CRUD and
similars) ?

[Frans Bouma [C# MVP]]

Bruce One wrote:

My ORM is responsible to map my tables to data object classes, but
then I face a big quizz: should I work with only this tier, putting
all my complex algorithms in this same tier, or should I create
another tier, above this DataObj class, to handle more abstract
methods (rather than CRUD and similars) ?

Different tiers allow you to create borders for functionality and
re-usability. If you're not going to reuse the tier, it's not that
necessary to go through the extra overhead and create new tiers.

Though you then might end up with a big piece of code which can do
everything, and that's perhaps a bit hard to maintain. So you should
make a list of pro-/con- items and then take a decision. THere's no
golden rule which says 'do this and it will be allright'.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------