“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
Every delay sucks, so whatever causes less delays rocks.
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.
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.
Working with JBoss, Seam, JSF and the Eclipse JBoss Tools...It's very painful. I had read about JRebel a couple of times on theserverside.com and javalobby and decided to give it a try. It works great.
Everyone who has tried it has fallen in love with it.
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 were attracted to JRebel because we had grown very frustrated with starting JBoss app sever constantly. After seeing JRebel mentioned in several blogs recently, we gave it a try. While it doesn't eliminate app server restarts completely, we only redeploy about 10% as much as before, saving both time and attention span!
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.
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.
Been using JRebel (http://jrebel.com/) for around 10 minutes now.. Feels like I have saved 11 minutes of redeploying time
Jrebel is pretty much well known but I never really considered trying & buying it because most of my projects were not so complex. Now I have a much bigger project and applying code changes becomes more difficult so I decided to give JRebel a try. So far, trial version worked perfectly.
I seriously cannot understand how I used to do my job without #jrebel.