If you are responsible for the technical infrastructure for the eCommerce and mCommerce of your company’s business, your job entails continual delivery of the site, functionality changes, and scaling the infrastructure to continue to enable and support business in the growth of the commerce of the business via electronic channels.
Say your team has completed a phase and the site has gone live. You probably have had an extremely busy schedule, to deliver a highly competitive functional and high performance site.
You have hopefully followed the methodology prescribed in the following presentation ‘WebSphere Commerce Tuning Methodology – Designing with Performance in Mind’, and if not, you have anyway had to go to and fro and eventually cover various aspects, in ad-hoc manner, to get to the performance and scale based on the non-functional requirements (NFR). You are now on your next mission/phase of your development and want to make sure that you apply the lessons learnt and do engage in a performance-centric development to avoid the madness.
I am consolidating my set of ground rule and 5 priority learning based on several consulting experiences for your WebSphere Commerce platform.
Ground rule: Performance Architect on board. Yes, you have a Solution Architect and the development lead, and they are extremely good. But with all the focus on functionality and the typical speed to deliveries, it is hardly feasible to expect them to wear the performance hat too.
1 – The development should call out the impact of enhancement(s) on the response time of the impacted scenario(s), High/Medium/Low
2 – Review of caching and SQLs for performance
3 – Single-user response time measurement against baseline benchmark
4 – A keen watch on the product fixes/APARs release by the product and apply what is applicable
5 –Load runs simulating the expected workload behavior on the site