The latest expert opinions, articles, and guides for the Java professional.

Top 3 reasons to use JRebel, QRebel, and XRebel

(This is a guest post from Dan Monahan, senior sales manager at Rogue Wave Software.)

Have you encountered a roadblock that’s getting in the way of reaching your development goals?

Odds are, a lot of other development teams are facing the exact same problem.

I’ve worked with hundreds of development teams around the world, and I’ve found common issues that they all must overcome to hit their goals and deliver high-quality applications.

Here are three challenges that I run into the most – and the solutions we’ve offered up to real customers to help them do better.

Elevating app performance while hitting sprint deadlines

Here’s a common scenario (i.e. nightmare) that most development leaders have faced…

Your sprint deadline is looming, and you haven’t run enough tests and made enough tweaks to guarantee that your app will function at 100%.

Do you extend the deadline? Or do you sacrifice quality and security?

Fast-approaching deadlines force development leaders to make difficult decisions, and your goal should be to minimize these trade-offs whenever possible. But armed with the right tools, development teams can both create quality apps and meet tight sprint and release deadlines.

QRebel helps find, diagnose, and fix performance issues in your testing environments, while XRebel offers real-time feedback about your application behavior and performance in your local machine. JRebel fast tracks Java application development by skipping the time-consuming build and redeploy steps in the development process. JRebel makes developers more productive since they can view code changes in real time.

Combining JRebel and XRebel has allowed software development company HyperProductive to save one hour every day – and better live up to its name. JRebel is used several times a day whenever code changes are made, and XRebel is used to find specific performance problems or to diagnose user-reported errors.

Creating a better user experience

Unfortunately, customer complaints are often the main motivation behind focusing on application performance. Production issues often aren’t resolved until the support line is flooded with complaints from end users. The key to mitigating these complaints and fostering a better user experience is shifting performance management to the left – i.e., finding, diagnosing, and fixing your application performance issues at the earliest possible point, in the development phase, well before they hit production and affect your customers.

QRebel shifts performance management to the left so developers find issues before they reach your customers. Unlike traditional APMs, which only allow you to get feedback from end users every application version, QRebel provides real-time feedback on performance pitfalls during coding, creating an instant feedback loop.

Software developer Antea regularly looks to optimize and update their development tooling to provide greater benefit to their customers. With XRebel, they have been able to increase their application’s performance to the point that even one of their sales representatives noticed and commented on it. They have less performance issues and are able to address them faster, resulting in fewer customer complaints about slow pages.

Enforcing performance requirements on every developer

One of the main challenges facing development managers is enforcing performance requirements on their developers. Development managers need to balance the technical requirements of their applications while keeping their developers happy and engaged. Some managers might find themselves in the position of only using tools that their teams ask for, lest developers get upset and leave. This may mean that not all your developers are using the best tools – and a chain is only as strong as its weakest link.

Even if nine out of 10 developers on your team are focused on performance requirements as they develop, the one who isn’t will negatively impact the rest of the team.

The solution is to pick a tool that both enhances app performance and makes life easier for the developer. No developer wants to be unproductive, but the more issues you let into production, the more resources they cost to fix, in both money and time – the developer’s time. Arming your teams with a performance-focused developer productivity tool goes a long way in preventing issues down the line that can take time out of every developer’s day.

Investing in developer productivity has helped ICON Health & Fitness mitigate potentially costly coding issues. The company frequently evaluates tools to help their developers both be more proactive and write better code. They chose to use XRebel to assist with the performance of their applications, from the session to the database, and to help them find exceptions and/or errors in their code. The tool easily lets any engineer verify that code in development won’t erupt with issues later on.

See for yourself how combining these tools can elevate app performance and accelerate productivity. Sign up for trials of JRebel, XRebel, and QRebel.

No Responses

No comments yet.

RSS feed for comments on this post.

Leave a comment