As an architect, one of my most critical activity is to regularly monitor my Java based web application’s health during business hours; identify performance bottlenecks and suggest remedial measures. Basically keep the engine humming sweetly without any hiccups. My application is monitored using dynaTrace. dynaTrace has been my trusted partner along with whom I have fought numerous performance related skirmishes and I have come to like it a lot. Recently my organization decided to do an enterprise wide APM roll out of the new kid on the block ‘New Relic‘. The aim of this blog post is to share with all my experiences and observations around the two APM tools, their design philosophies and their differences. My observations are solely in the context of web application performance monitoring, pure Java application monitoring is a completely different ball game.
In my role as a Java Technical Architect, I am forced to wear different thinking hats. Some times I am a Solution Architect, Subject Matter Expert on some technology and the last few days I have been wearing the hat of performance tuning expert. Today I am going to pen down some thoughts around what a person should focus on once he or she is by design or default selected to tune an application.