“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 90+. The company’s commercial 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.
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 and intrepid operations folks who keep existing Java apps humming (and up-to-date). You know, people like us. Here’s what some of them have said about life with tools we’ve made.
WHAT THEY SAY
I was attracted to JRebel because of its transparency, simplicity and efficiency. It's easy to set up and very nice to use!
JRebel is so important to us, we really love it.
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.
JRebel is one of the best utility I've ever seen. We have just met JRebel and loved it.
Stopping and start my container 10 times a day is the most annoying thing in the Java world. Finally I hope I have found the solution with JRebel.
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.
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.
I seriously cannot understand how I used to do my job without #jrebel.
JRebel is really an amazing tool.
Given the nominal cost of JRebel and the huge amounts of time it saves, I would not consider developing Java EE applications without it.
Over the last 265 days JRebel prevented at least 1,209 redeploys/restarts saving me about 49 hours.
Since migrating to IBM WAS 7.0, we've had trouble with replacing HotCode - we're now using JRebel for uninterrupted development and it's working fine :)