AppDynamics Review

I see plenty of benefits in using AppD for any old school build of applications, but transactions are not collected across the board when architected with micro services

What is our primary use case?

Java application instrumentation across a microservices architecture build.

How has it helped my organization?

When adopting / implementing a micro services application stack, you have to get all of the services to move / upgrade at the same time. This has led to a disjointed implementation of AppD. Disjointed implementations of tools do not lead to home run capabilities to build / run / operate.

What is most valuable?

Insights outside of the code we write. We find some of our adopted libraries perform sub-optimally. Sub-optimal performance leads to a search for alternate libraries to help us scale.

What needs improvement?

Transactions are not collected across the board. Your application needs to fail before AppD starts collecting deep metrics.

For how long have I used the solution?

Three to five years.
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More AppDynamics reviews from users
...who work at a Financial Services Firm
...who compared it with Dynatrace
Add a Comment