Transaction Tracing Helps Developers Optimize Code as They Write It
With transaction tracing tools, developers can continually be looking for performance problems in their code as part of their natural development process.
Join the DZone community and get the full member experience.Join For Free
The best time for developers to optimize their code is while they are writing it. Developers can leverage the detailed transaction tracing available from APM-type tools like Prefix as a fast feedback loop to understand what their code is doing and how long it takes. Prefix works as an ASP.NET profiler and also works with several common JVMs for Java.
Transaction Tracing Is a Critical Feedback Loop
“When informed about a problem whilst in the moment, I’m in a much better position to make corrections or come up with alternative solutions. Without a quick feedback loop, the passing of time makes it difficult to get into the initial mindset which caused the problem to begin with.” — Vince Panuccio
Lightweight code profilers and other data collect methodologies can be used to provide developers a wealth of information about what their code is doing — including logging statements, errors, SQL queries, web services, and other dependencies.
Today’s applications are complex and typically connect to multiple dependencies like SQL and NoSQL databases, PaaS services, MongoDB, Elasticsearch, Redis, queueing, and many other services. Prefix helps developers instantly understand if their code is using them correctly and how they impact the performance of their app.
Example transaction tracing captured by Prefix.
As an example, developers can find common problems like N+1 database query patterns caused by SQL queries being run in a loop. Prefix’s built-in suggestions highlight a potential problem — and the 38 database queries become a glaring problem.
This instant feedback can help developers validate that their code is doing what they expected it to do. Profiling and performance tuning is something developers don’t typically do until the tail end of a project. Most of the time, they don’t even do it unless there is a known performance issue in the code or they are doing stress testing.
By using tools like Prefix, developers can continually be looking for performance problems in their code as part of their natural development process. The transaction tracing that developers can get from these types of free tools is a must have.
Published at DZone with permission of Matt Watson, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.