“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. Operations teams run LiveRebel to eliminate server downtime during live-app updates.
The result? Happy coders writing and testing beautiful code. Happy operations teams running beautiful code. And 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
JRebel is really great - it helped our team save a lot of hours!
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 was attracted to JRebel because of its transparency, simplicity and efficiency. It's easy to set up and very nice to use!
Over the last 265 days JRebel prevented at least 1,209 redeploys/restarts saving me about 49 hours.
Every java dev should have a copy of #jrebel installed. Buy it yourself if your workplace is cheap. It's soo worth it.
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 :)
JRebel has the ability to change code dynamically when the program is running or during a debug session, which I have been looking for a long time. I am sure it will save a lot of development time, especially when the size of the project is large.
We’ve had some real OutOfMemory problems in our production environment for quite some time. Once I got XRebel up and running I noticed that our most used webapplication uses around 15MB/User session. By tuning a few JSF parameters I got the average user session from 15MB to 0,5MB.
JRebel is one of the best utility I've ever seen. We have just met JRebel and loved it.
JRebel saves a lot of frustration from dealing with JSF, JPA and Tomcat. One big thing is I don't need to start Tomcat every time to see my code!
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 heard about JRebel from my colleague who highly recommended using it. After trying it out a couple of times, it made perfect sense to me, and I haven't looked back since. Great product.