Debugging and troubleshooting distributed applications

Traditional debugging and troubleshooting of on-premise applications is through the IDE-based Java debugger option to run the application in debug mode with the visibility to the executed code path. For example, a desktop application in-house to an organization to manage their employee information can be developed and tested in a single IDE and debugged through the Java debugger option. However, this approach doesn't let us review the application performance, and has a restriction to replicate the production application issues and distributed issues.

One traditional approach to review the issues is through analyzing the log files during the defect timing. This allows the production application logs to be reviewed for identifying the actual issues; however, it is very time consuming having limited scope and visibility with high performance impact based on the IO.

The distributed application debugging and troubleshooting involves the review of concurrent execution issues, including deadlocks, raise conditions, and unexpected complexity. The high data volumes on which the distributed applications are running needs to be considered. They are constantly increasing the impact on multiple resources; however, the resources are very limited and have the risk of starvation.

DevOps is the way to go for next generation cloud distributed applications, with the development and operations teams working together with the real-world tools and techniques to perform the build, deploy, and test the applications on the cloud distributed infrastructure.

AppDynamics is a tool to review the application performance management on the production environments by monitoring the systems to provide the right information rather than reviewing the issue after it has happened.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset