Hi,
I believe that usually, when you implement a design pattern to maintain testability, scalability, etc. it's common to experience a small decrement in the application's performance when compared to an implementation without any pattern. How significant this performance decrement will be depends of the context of your application; for most scenarios it should be minimal.
However, in this particular case, I do not understand why returning an IEnumerable<> would impact in the performance of the application at all. Could you elaborate a little more about how this is affecting the performance and what implementation would you prefer to return instead?
Thanks,
Damian Cherubini
http://blogs.southworks.net/dcherubini
I believe that usually, when you implement a design pattern to maintain testability, scalability, etc. it's common to experience a small decrement in the application's performance when compared to an implementation without any pattern. How significant this performance decrement will be depends of the context of your application; for most scenarios it should be minimal.
However, in this particular case, I do not understand why returning an IEnumerable<> would impact in the performance of the application at all. Could you elaborate a little more about how this is affecting the performance and what implementation would you prefer to return instead?
Thanks,
Damian Cherubini
http://blogs.southworks.net/dcherubini