New Relic vs Stackify: What are the differences?
What is New Relic? SaaS Application Performance Management for Ruby, PHP, .Net, Java, Python, and Node.js Apps. New Relic is the all-in-one web application performance tool that lets you see performance from the end user experience, through servers, and down to the line of application code.
What is Stackify? Performance. Metrics. Errors. Logs. One platform. Stackify offers the only developers-friendly innovative cloud based solution that fully integrates application performance management (APM) with error and log. Allowing them to easily monitor, detect and resolve application issues faster.
New Relic and Stackify can be categorized as "Performance Monitoring" tools.
Some of the features offered by New Relic are:
- Performance Data Retention
- Real-User Response Time, Throughput, & Breakdown by Layer
- App Response Time, Throughput, & Breakdown by Component
On the other hand, Stackify provides the following key features:
- Application Performance Management (APM), Custom metrics, Log management. Application monitoring
- Server Monitoring
- DB & queries monitoring
"Easy setup" is the top reason why over 411 developers like New Relic, while over 7 developers mention "Error tracking" as the leading cause for choosing Stackify.
What is New Relic?
What is Stackify?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Stackify?
We were looking for application performance management solution (APM) for our .net. We were using New Relic's free version but it wasn't cutting it and we were missing some capabilities. Stackify's solution is great and as a bonus we got their log management and exception aggregation tools that are integrated with the APM. Plus the team at Stackify was very helpful
Stackify does a great job at providing lots of useful information without it becoming overwhelming. All of the features are well thought out and it has proven very helpful at diagnosing and preventing bugs in our application.
Free Heroku add-on. Not particularly useful for us. Rails profilers tend to do a better job at the app level. And I can never really figure out what’s going on with Heroku by looking at New Relic. I don’t know if we’re just not using New Relic correctly or if it really does just suck for our use case. But I guess some insight is better than none.
How do you know what parts of the workflow need improvement? Measure it. With New Relic in place, we have graphs of our API performance and can directly see if a server or zone is causing trouble, and the impact of our changes. There’s no comparison between a real-time performance graph and “Strange, the site seems slow, I should tail the logs”.
We monitor and troubleshoot our app's performance using New Relic, which gives us a great view into each type of request that hits our servers. It also gives us a nice weekly summary of error rates and response times so that we know how well we've done in the past week.
I'm trying to wring more instrumentation out of New Relic as it pertains to Rack, but for the time being, New Relic is monitoring/alerting uptime and some basic performance metrics.
Just like we care about errors, we care about metrics - especially around performance. You'd be crazy not to use it - and not surprisingly, it's a one-click add-on in Heroku.