JRebel Reviews & Insights

Score8 out of 10

10 Reviews and Ratings

Community insights

TrustRadius Insights for JRebel are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Efficient Integration with Popular Java Development Tools: Users have found JRebel to be a simple and efficient platform for Java application development, thanks to its integration with popular Java development tools like IntelliJ IDEA, Eclipse, and NetBeans. This seamless integration saves users time by allowing them to work within their preferred IDE without any disruptions or compatibility issues.

Real-Time Code Testing: JRebel's ability to test new code immediately has been highly appreciated by users. By eliminating the need for redeployments, JRebel reduces the risk of introducing bugs and errors into the codebase. Some users have stated that this feature has significantly improved their productivity and allowed them to focus more on writing high-quality code.

Time-Saving Redeployment Elimination: One of the standout features of JRebel is its elimination of redeployments. Users appreciate how this feature saves them plenty of time by providing real-time visibility of code modifications and clarity on their impact on application environments. The elimination of redeployment not only improves productivity but also reduces frustration for team members and eliminates context switching issues.

Reviews

3 Reviews

Be more productive, happier, save money. Be JRebel.

Rating: 10 out of 10

Incentivized

February 1, 2019

Use Cases and Deployment Scope

We use JRebel in the software development group to minimize the time spent between the redeployments of the Java applications during development. Without JRebel, every change you do in the source code that requires re-compilation will need a redeployment of the entire app, which can take from 30 seconds to several minutes. When you do this only to test something or to visualize a small change in the user interface, the time needed for redeployment it is simply wasted time. JRebel removes the need to redeploy which improves development speed, reduces people's frustration, enhances the productivity and saves the company money.

Pros

Removes the time needed for redeployments of the source code - improves productivity, time to market, and saves money.
Easy to install
License renewals - the sales department reaches out to you long before the licenses expire so you can have time to get your approvals.
Analytics and reporting - it will show you the time saved by JRebel and even the ROI, if you input the average hourly cost of a developer.

Cons

In multi-project environments, the dependencies are not always reloaded.
License management - we use a license server with a combination of dedicated licenses and floating. I had some struggle managing these due to the License Server User Interface not being very intuitive.

Likelihood to Recommend

I recommend JRebel for Java developers, it will remove the time needed for redeployment, it will increase the focus on the task at hand (without being distracted by the redeployment) and will make them happier.

I recommend JRebel for Java Development Managers, they should purchase this for their teams - it will increase productivity, decrease the product's time to market, and it will save money for the company. The ROI can be calculated upfront and presented to higher level management for approving this, if needed.

Cristian Bodnarasec

Senior Software Development Manager in Information Technology at eSilicon (501-1000 employees)

Vetted Review

4 years of experience

View profile

More consistent short development cycles than Instant Run...a must when doing backend code

Rating: 8 out of 10

Incentivized

August 22, 2017

Use Cases and Deployment Scope

It's being used by a few of our Android developers. It allows them to minimize compile/deployment time of Android apps during the development process. Android Studio has support for something called "Instant Run" but it tends to do full compiles quite a bit more often then JRebel does, so using JRebel minimizes our debug deployment time.

Pros

Deploys all layout changes consistently (when Instant Run was initially available, you couldn't tell if the change you made to a layout was actually being tested or not).
Doesn't require a full build as often as Instant Run when changing code.
Works with compile time annotation libraries like Realm, etc.

Cons

Launch times are where JRebel is slower than Instant Run.
Sometimes, it has incompatibilities with how you wrote something and causes compile failures, but Zero turnaround is quick to respond.

Likelihood to Recommend

Minimizes debug/deployment cycles when you're making a lot of changes to your Android code.
If your app is small, Android Studio's Instant Run is faster.

Ken Yee

Android Architect in Engineering at KAYAK (51-200 employees)

Vetted Review

1 year of experience

View profile

Fastest redeploy ever

Rating: 8 out of 10

Incentivized

June 10, 2016

Use Cases and Deployment Scope

I used JRebel to redeploy our web application on the fly. It was used in a specific project. We had problems redeploying the application because it was very huge and it took a lot of time. With Jrebel we were able to make it in a very fast way, saving many many hours.

Pros

Fast redeploy

Cons

It worked great, no big cons

Likelihood to Recommend

It is a great software which works well in all areas in which you need to redeploy the application very often for some reason. You might have been developing the application and for some reason it's hard to test automatically, so you need to see the result of your code quickly.

Verified User

Engineer in Information Technology (201-500 employees)

Vetted Review

1 year of experience