“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 60,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
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.
I was attracted to JRebel because of its transparency, simplicity and efficiency. It's easy to set up and very nice to use!
Just started using JRebel; installation was done in 15 minutes and 1 hour later it saved me 20 minutes of restart time.
Like a fish rediscovering water.
Been using JRebel (http://jrebel.com/) for around 10 minutes now.. Feels like I have saved 11 minutes of redeploying time
Given the nominal cost of JRebel and the huge amounts of time it saves, I would not consider developing Java EE applications without it.
Saving time with JRebel is so amazing. No more redeployments... Refactoring classes, Refresh the page and that's it! Amazing stuff!
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'm afraid our developers might go for a strike if we say to them, ‘Hey, we're not going to use JRebel anymore.
Why isn't JRebel part of the standard Java SDK?
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.
Since evaluating JRebel, we have seen redeploy times significantly reduced and I am therefore hoping that we can be more productive and turn around our development projects in a quicker timeframe.