/ Gartner Magic Quadrant for Application Performance Monitoring 2013 ~ Java EE Support Patterns


Gartner Magic Quadrant for Application Performance Monitoring 2013

As IT architects and consultants, it is crucial to ensure a highly performing, stable and scalable production environment for you client applications. Proper monitoring along with a comprehensive capacity planning model is crucial in order to achieve such goals.

While most performance data can be extracted at runtime through various OS commands and open source tools, large and complex IT production environments often requires the deployment of commercial grade APM solutions for an efficient management of the operations.

Before providing recommendations to your client and purchase the first APM product you find on the Web, it is important to properly review the different APM solutions and compare their product capabilities vs. your client operation needs and budget.

A trusted source of information I have been following since a few years now is the Gartner Magic Quadrant report for APM. Gartner’s APM yearly report is essentially an extensive research of every vendor that meets their qualifications. The process also includes customer interviews. The final report places each vendor on two axes, Completeness of Vision and Ability to Execute, and then places them accordingly on a Quadrant. If not done already, I recommend that you obtain your own copy of the 2013 report.

I will publish more articles this year and share my recent experience with top APM solutions such as New Relic, AppDynamics, Compuware DynaTrace and Dell Foglight.

Please do not hesitate to share your experience along with your constructive comments on APM solutions.



This is quite interesting data. We are also checking dynaTrace and AppDynamics. Need to see how much overhead they cause and what amount of visibility they can give us...:)


From my experience, both products have low overhead and provide deep visibility of your Java application performance. I would recommend either product.

That being said, based on my experience, dynaTrace requires a little more learning curve but if you have the right people with the right skills it won't be a problem.

Both products are scalable and designed and able to handle large IT enterprise environments.


^^Like I said before, probably we are going to choose appdynamics...if money is not the problem :)
on our app, dynatrace has bit more overhead on transaction time compared to appdynamics...
but personally, I like dynatrace...it has great features...from end user session to DB level info...that's incredible...probably that is why it is bit heavy on the app...let's see!

AppDynamics is definitely a great pick.

DynaTrace features are indeed quite powerful, their internal end to end PurePath feature for transaction breakdown analysis is one of the finest in the APM industry.


Thanks for a great read ! AppDynamics is a good fit for organisations that have complex, distributed application architectures which rely solely on Java and .NET technologies.

DynaTrace is best tool among all other , they have much more better capabilities in end to end perfomance monitoring.

See https://docs.appdynamics.com/display/PRO41/Monitor+Development+Environments - overhead of AppD is comprable to Dynatrace just because AppD monitors every 1000th transaction and DT monitors each of it or so. Try to enable 100% visibility in App (by enabling "development mode") that DT is normally doing out of the box and only then compare overhead. DT does not have anything like "development mode" - always 24/7 for each agent.

Thanks for the points and link on App Dynamics regarding DEV vs. PROD mode. The DEV mode is ideal for deeper profiling before new releases are pushed to production.

Post a Comment