“Software is eating the world,” said Netscape founder and tech investor Marc Andreessen. Line by line, hardware is being consumed by code, and Java is spoken by a massive army of hungry mouths.
However, since the programming language was introduced in 1996, developers have had to write Java code on their own machines and then upload their code to remote servers for testing.
The idea that would become a glass of ice water to coders in redeployment hell was born in Estonia in 2006. That’s when Jevgeni Kabanov found a way to address Java’s core problem – the redeployment bottleneck. His insight led to a start-up and two products that smart Java teams wouldn’t be caught without. In other words, magic happened.
Developers at thousands of companies around the world use JRebel to instantly view code changes without redeploying the application server.
The result? Happy coders writing and testing beautiful code. Happy customers enjoying time and money saved through all that beautiful, productivity-boosting code.
Today, ZeroTurnaround is the labor of love by a global team of 150+. The company’s go-to-market heart beats in Boston, Massachusetts, while our development feet are firmly planted (and rapidly growing) in Estonia, at two offices in Tallinn and Tartu. We also have a branch in Prague, Czech Republic.
We are dedicated to making developers lives better, and we now have over 65,000 active users at 5,200+ customers, including 36% of Fortune 100, in 80+ countries.
DEVELOPERS SAYING REALLY NICE THINGS
We’re developers who make stuff for people just like us. Yes, our software is used by companies, from startups to well-known multinationals. But at their core, our products are consumer products. It’s a stroke of good fortune that our “consumers” happen to be other Java developers. You know, people like us. Here’s what some of them have said about life with the tools we’ve made.
WHAT THEY SAY
Every java dev should have a copy of #jrebel installed. Buy it yourself if your workplace is cheap. It's soo worth it.
I just hated the whole Eclipse IDE and one of my co-workers suggested I try Jrebel since 40% of my time was waiting on Eclipse to build and run. With Jrebel, things are going much smoothly now.
Jrebel is pretty much well known but I never really considered trying & buying it because most of my projects were not so complex. Now I have a much bigger project and applying code changes becomes more difficult so I decided to give JRebel a try. So far, trial version worked perfectly.
I'm afraid our developers might go for a strike if we say to them, ‘Hey, we're not going to use JRebel anymore.
Con JRebel, salvar un archivo en el IDE y ver mis cambios inmediatamente en la pagina sin tener que volver a hacer "deploy", no tiene precio.
Over the last 265 days JRebel prevented at least 1,209 redeploys/restarts saving me about 49 hours.
We found some very interesting side-effects right away. The worst of those was some badly coded Hibernate which would generate over 700 database queries. The JSF memory footprint was a bad surprise - some beans are in the session, that shouldn’t have been there.
The difference between half minute and half second is not 29,5 seconds, but the feeling of coding freely and without pauses. I just follow my thoughts. That's it.
The developers at BlackBeltFactory.com use JRebel and although I probably could have gotten it for free from the ZT guys, I wanted to pay for this fantastic product.
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.
I am so much more productive with Java, JPA and Spring (and JRebel) than i was with RoR the last months… It's really fun again.
I see JRebel as this "missing piece" in the whole picture where we could see Java-stack not only as a stable, well-tested environment to build applications on but also as a rapid development environment.