Be more productive, happier, save money. Be JRebel.
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.
