Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.
See all our reports

5 Reasons why every Java EE developer should use XRebel

Here is a story from a year ago, much before I became Product Manager of XRebel, even before I knew Zeroturnaround. This incident just might have influenced me in taking the job as well.. :) It was Memorial Day weekend and we had friends from New Jersey visiting us. We had fun on Friday and Saturday and then came a series of beeps on my husband’s phone – his pager duty alerts – Yes production issues and several of them.. Did I mention he is a java developer? He had to abandon our Sunday plans and get to work :(.

How many of you are thinking, “I’ve done that” , “been there” …?

There are several reasons that can cause such issues and many of these are quite inevitable and a natural part of the development process. But there are also many issues that can be caught and solved during development so you can avoid them in production.

Profilers serve as handy helpers in finding and fixing issues before they cause production failures. Most java profilers are great about giving a lot of information but it can also be too much information depending on the issue you are trying to find and solve. This information might be of little or no use if you are not quite sure what you are looking for.

Almost all java profilers also require that you stop writing your code and run your application through the profiler – breaking the development flow. We ran a study recently that showed developers need anywhere between 2 min and 20 min to “get back in the flow” if their work is interrupted. Additionally, leaving your development environment to use a profiling tool is not very conducive to making iterative changes to your application especially in cases when the changes are simple enough like when solving the issue requires changes to a few lines of code.

Would it not be handy to have a tool that is your little helper that not only finds issues with your application, but is simple and lightweight and can display issues in a straightforward way – right in your browser?

Good news is that, such a tool exists and it is called XRebel!

Think of XRebel as a developer’s little helper – a that runs alongside your application as you are developing code. It is like having a buddy looking over your shoulder to catch issues. XRebel works hard in the background and then alerts you when any issues are detected. All alerts and reports are displayed right on your browser. The issues could range from an exception that is hiding from plain sight to memory hogging large sessions.

Here are some features of XRebel that are pretty much specifics of what you can do with the product:

  • Profile JDBC and NoSQL databases
  • Find web service bottlenecks
  • Identify N+1 queries
  • Understand session footprint
  • Track down hidden exceptions

Coming back to the 5 reasons that I wanted to talk about.. as a JavaEE developer using XRebel, you will be able to

  • Deliver better code faster
  • Develop reliable code
  • Become more efficient
  • Be Proactive, not Reactive
  • Analyze performance issues easily

Why wait? Download XRebel for free and gone will be the days when you were asked to come into work on a weekend or holiday and you can go home on time!

GET ME TO XREBEL!

  • Ian Kaplan

    I’m really not convinced. I’ve looked around the site and it’s still not clear to my why I’d like to use this tool, especially in the case of my Amazon Web Services hosted application (running on multiple Tomcat instances behind a load balancer). You’ve used up your quote of my time as well. I don’t really want to have a long discussion about who great your tool is when it’s not obvious from your web site.

  • A tutorial post for XRebel wrote in Chinese:
    http://aboutcoder.com/2016/08/26/xrebel-tutorial/