“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.
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'
Every delay sucks, so whatever causes less delays rocks.
Just a few compiles without having to deploy was enough to convince me to buy JRebel.
JRebel is easy to use right out of the box and fun to work with. It saves a lot of time in the development phase!
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.
I have been very impressed with JRebel, wish I had come across this product a lot sooner, would have saved me so much time/boredom waiting for so many container restarts.
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.
It used to take 5 mins to rebuild and restart the server - now we see changes pretty much instantaneously. I saw the value right away.
I seriously cannot understand how I used to do my job without #jrebel.
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.
JRebel is so important to us, we really love it.