
Singleton design approach
We are not sure whether we am getting this right regards
the Singleton Object.
Intially we thought it would be a good idea to have our
Business & DAL objects
as Singleton Objects with static methods so that there
isnt an overhead to instantiating them.
But decided against that pattern after hearing that all
such static methods will just have a single thread of
execution is this true and wouldnt service more than one
client at any given time.
What are the pros and cons of using such a design
approach.
Will there be any scalability issues since there is just
one instance maintained in a Singleton approach.
Well the Application blocks helper classes from Microsoft
seem to follow this approach.
we are worried whether such objects will be able service
multiple client requests simultaneously
Any sample illustrations would be higly regarded
Regards
Bijoy