Over 4500 Awesome Clients
These customers seriously like what we do.
Here is what our users say about us
We were attracted to JRebel because we had grown very frustrated with starting JBoss app sever constantly. After seeing JRebel mentioned in several blogs recently, we gave it a try. While it doesn't eliminate app server restarts completely, we only redeploy about 10% as much as before, saving both time and attention span!
Every java dev should have a copy of #jrebel installed. Buy it yourself if your workplace is cheap. It's soo worth it.
So far, everybody I speak to about JRebel is satisfied with it - frankly, I cannot believe nobody thought of JRebel before.
Our normal build-deploy cycle would take about 25 seconds. On average, JRebel saves one developer from 10-12 builds per hour. That's roughly five minutes per working hour or 30-35 minutes a day per developer.
Why isn't JRebel part of the standard Java SDK?
Given the nominal cost of JRebel and the huge amounts of time it saves, I would not consider developing Java EE applications without it.
I seriously cannot understand how I used to do my job without #jrebel.
JRebel seems to be the only cost effective way to accelerate the compilation and startup of our projects, consisting of several EAR artifacts deployed on a JBoss App Server. We have been using it for a year, and my development team is very pleased with it.
We’ve had some real OutOfMemory problems in our production environment for quite some time. Once I got XRebel up and running I noticed that our most used webapplication uses around 15MB/User session. By tuning a few JSF parameters I got the average user session from 15MB to 0,5MB.
Every delay sucks, so whatever causes less delays rocks.
Alterar método, adicionar atributos, criar classes, restart servidor, isso era um ritual a cada hora do meu trabalho. Com JRebel posso alterar qualquer código java que já é refletido na aplicação em funcionamento. Muito bom.
Setting up JRebel was completely painless and my questions on the support forum were answered quickly. The performance gains were immediately obvious to us, so after the evaluation period was over we decided to purchase licenses for all our developers.
We are writing up loads more case studies now. If you'd like to be one of our case studies, please contact firstname.lastname@example.org