Over a million developers have joined DZone.

Cross App Tracing: Time to Break Up that Huge Rails Application?

DZone 's Guide to

Cross App Tracing: Time to Break Up that Huge Rails Application?

· Performance Zone ·
Free Resource

RailsConf 2013 logoThis post comes from Sam Goldstein at the New Relic Blog.

RailsConf 2013 is right around the corner! And to celebrate, we’re publishing a series of blog post that highlight what’s new and exciting in the world of New Relic’s Ruby support.

If you’re a Rails developer, you know that developing a great web app is a straightforward process. While that offers many advantages, some apps grow too large and become hard to manage.

This means you’ve mostly likely had at least one encounter with a huge monolithic Rails application. And breaking up these apps has become a common topic at Ruby conferences this year. At Ruby on Ales, Software Developer Brian Morton explained how Yammer breaks applications into services. (He’ll be giving the same talk next week at RailsConf.)

To help you stay in control of your applications, New Relic’s Ruby Agent now provides Cross Application Tracing (CAT) which tracks and visualizes how different services in your infrastructure communicate. In addition to tracking across Ruby apps, we can trace API calls made to Java, Python, PHP, or .NET apps. For example, you can use CAT to see related Transaction Traces between a Rails application and a high performance Java service.

CAT Transaction Traces

Use CAT to get some good insight into how data is flowing between your applications. It’s been helpful to us for breaking apart our own gigantic Rails app.

For more information on New Relic’s Ruby agent, check out:

* rubygems.org
* github.com
* newrelic.com

Next up: Thread Profiling: See Exactly What Your App Is Doing


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}