Hello,
My team and I are begining to experiment with CSLA for an upcoming project. The big question for us (especially due to the nature of the project) is performance. Are there any performance concerns with CSLA or any tips, best practices for CSLA to improve performance?
Thanks,
Ank
CSLA is very high performance.
Datasets are significantly slower.
Joe
I found this significantly useful...
CanReadProperty performance heads-up
http://forums.lhotka.net/forums/thread/16637.aspx
and this too...
Performance of creating large collection
http://forums.lhotka.net/forums/thread/4044.aspx
I think for the most part considerations of performance go far beyond CSLA or DataSet.
This might involve making good use of caching, making sure one retrieves the right amount of data to get the job done, preparing the proper indexes for SQL, ... I truly do not believe that deciding CSLA or not CSLA has as anywhere near as much play on performance as the actual programming.
I will say this - I wholly believe that it is entirely possible to build a good performing CSLA application as much as it is entirely possible to build a good performing "data-centric" or alternative business object approached business layer. That said, i think it's entirely possible to build a bad performing CSLA application (and data-centric application).
In all sincerity I do not believe performance is a problem you will find with the CSLA framework if used properly. I think the reason one chooses CSLA is if they want to enable a strong business layer in their application. In our case, that is why we chose CSLA.
Chris
skagen00:
I think for the most part considerations of performance go far beyond CSLA or DataSet.
This might involve making good use of caching, making sure one retrieves the right amount of data to get the job done, preparing the proper indexes for SQL, ... I truly do not believe that deciding CSLA or not CSLA has as anywhere near as much play on performance as the actual programming.
I fully agree with this statement as well, since by performance I believe you are mostly referring to DB interaction time (ie how long it takes to perform search, save etc actions).
CanReadProperty performance heads-up
I found the above to improve performance as well but more on the UI domain (rendering my custom user controls).
Finally, consider what type of dataportal you will use. There are pros and cons in either approach and sometimes you have to compromise in some domains in order to achieve maximum performnace. But more on that in Rocky's book.
Copyright (c) Marimer LLC