> > The point of using objects is that you can pass a completely
> > structured object containing the data to the Java layer of the
> > application.
> >
> > Objects can not only be data structured and also contain other
> > objects.
> >
> > In terms of maintenance, a highly modular multi-tiered approach of far
> > better for maintenance than a flatter 2-teir traditional architecture.
> > The point of multi-tiered applications is that every bit of code is in
> > its correct place, DML in the table encapsulation layer, objects in
> > the object layer, business logic in the java layer, and so on...
>
> And when you start passing large numbers of rows between the database
> and the front side application ... no problems whatsoever no sirree
> bob!
>
> And those objects that span multiple tables in the database ...
> nothing bad can happen there at least.
>
> Business logic in the java layer? No problems at all with designs
> like that ever!
At a high level, this makes sense, but have you compared performance
using different approaches?
Received on Fri Feb 02 2007 - 09:13:37 CST
