CSLA based architecture versus Data-centric architecture

jrlopher posted on Sunday, July 08, 2007

Hello all

       I have been working with csla for two years, but now I'm going to work for a new software company that uses a data-centric architecture. This company uses a layered architecture with the following structure:

    UI
    Web Services
    Facade
    Business Rules
    Data Access Layer
    Data

    The UI invokes a method on a web service that normally produces a call on the data access layer to obtain a dataset with the data (or to update data from a dataset). This folks don't use oop at all, and I miss it very much. I want to propose the CSLA framework to use a more object oriented aproach to design solutions, but I don't know how to maintain the web service layer without hit the performance of the application. With the datasets this people reduce at minimum the access to the database, however, with the csla each entity needs to access the database to obtain its data (thus calling many times the web service layer).

Please I need a little bit of help.

Thanks and sorry for my english.

-----------
Jose

ajj3085 replied on Monday, July 09, 2007

Well the web service will always be slow from a performance angle.  If you want to use Csla, your best bet would be to throw out the web service completely, and the facade.  The goal of OO would be to build a more maintable application, but if they don't see any problems maintaning the current application, you may be hard pressed to convience them to change.