Serialization Performance

mharper posted on Friday, July 14, 2006

I’m in the progress of designing a web application that uses the CSLA architecture.  The initial physical structure will contain one server for the UI, Business, and the Data Access Layer and a second server for this database.  With this physical structure, there would be no need for serialization.  I am considering leaving in the serialization functionality within the code in the case that we split out the UI from the Business Layer at a later date.  Would this create degradation in performance?

 

Thanks,

M. Harper

xal replied on Friday, July 14, 2006

M,
Serialization doesn't take place if you use the simple dataportal. Just put the sqlconnection string in your web.config and communicate directly to the db.

Andrés

Brian Criswell replied on Friday, July 14, 2006

The serialization code does two major things.  It handles remoting and enables the undo functionality.  However, like much of Csla, it does not cost you if you do not use it.  In your scenario, the calls will be made straight to the database without involving serialization.  You probably should leave it in while you are learning the framework.