Pradeep, I would dare to say that most design patterns do not decrease performance in any significant way. An extra method call costs close to nothing.
Your session facade probably is helping you, but your business delegate probably isn't. (based on my experience)
It does hide the EJB layer (Lookup and exception hidden). My question how big is this advantage?
Originally posted by Lasse Koskela:
I'd be interested to hear about particular patterns that degrade performance somehow significantly because I can't think of any. (I could browse the bookshelf but I'm too lazy to do that...)
Originally posted by Pradeep Bhat:
[QB]Patterns does increase the complexity of the system but does maintenance easier. Some patterns increase overhead ...[QB]
Should the issues related to design patterns be almost entirely left to the architect or are they just as important for developers?
Originally posted by Faisal Khan:
I thought, I may not have made full sense. My question, I guess really is, should I be using scenario 1 or 2 above from a good design perspectve.
That is, should I continue down the path of having one Database.class with a method performQuery( String query ) and all my classes use this class for querying the DB.