Search This Blog

Thursday, 16 September 2010

Design for Performance – Why don’t we get it right?

In the modern day enterprise, building efficient applications as a composition of cooperating components depends significantly on having a thorough knowledge of both, component performance, as well as component interactions. Hence, to make effective design decisions concerning configuration, deployment and interconnection, it is important to compliment the traditional application development processes with 'performance centric' methodology.
This seems to be ignored without knowing the additional cost which organisation has to pay in re-engineering the applications. I find it very interesting when I see these challenges repetitively in almost every implementation. Why don't we ensure that enterprise applications are designed for performance and delivery processes are performance-centric? What is the missing link of the Jigsaw?


  1. Because lack of future vision or ignorance causing this issue most of us want to finish project with prescribed time and money.

  2. My view is it's a gross underestimation of the requirements coupled with ambitious business plans despite limited resources. A well thought through solution should be able to trace every system performance requirement to a relevant business requirement and to be able to call out 'cans' and 'cannnots' in achieving them. It's easy to discount something as 'it only happens in a perfect world', but governance without it's teeth to pushback or stop incompetent systems has to finally chew it's own tongue!