“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
Like a fish rediscovering water.
Over the last 78 days, JRebel prevented at least 1774 redeploys/restarts, saving about 71.9 hours!
Why isn't JRebel part of the standard Java SDK?
With JRebel, I am able to see code changes more or less in real time - JEE development is a joy once more!
We are all very happy with the fact of not wasting time on things that are not coding and finishing things.
To whomever tells me 'I don't have time to lose trying to use JRebel', I would say 'You're actually losing time by NOT using it'
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.
We found it very useful to dig into the SQL queries. We quickly found some very lengthy and complicated queries. We also found that our session can get as large as 30 Mb - we had too many references to Spring beans in the session.
JRebel has made my life so shiny happy. It auto deploys updated classes and JSPs. Holla!
Just a few compiles without having to deploy was enough to convince me to buy JRebel.
The time period between making a change, rebuilding, deploying and restarting the container has always been a sticking point with me, but JRebel allows me to develop constantly without bouncing back and forth. Personally, it's one of the more important pieces of software I've come across in quite some time.
JRebel has transformed a nightmarish 10-minute modify, compile and debug cycle to a matter of seconds. Thanks for giving me back my sanity.