“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
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!
Been using JRebel (http://jrebel.com/) for around 10 minutes now.. Feels like I have saved 11 minutes of redeploying time
Over the last 78 days, JRebel prevented at least 1774 redeploys/restarts, saving about 71.9 hours!
JRebel is like a drug for me, I am totally addicted to this tool because it saves a lot of nerves and energy and it is exactly what I need to speed up the software production process for my application.
I was attracted to JRebel because of its transparency, simplicity and efficiency. It's easy to set up and very nice to use!
Given the nominal cost of JRebel and the huge amounts of time it saves, I would not consider developing Java EE applications without it.
We had a need for faster turnarounds since we have huge projects that take ages to build and deploy. Jrebel is an excellent tool to reduce that time:)
JRebel has made my life so shiny happy. It auto deploys updated classes and JSPs. Holla!
JRebel seems to be the only cost effective way to accelerate the compilation and startup of our projects, consisting of several EAR artifacts deployed on a JBoss App Server. We have been using it for a year, and my development team is very pleased with it.
It not only takes me at least 2 minutes to redeploy, but it adds another 5 minutes to get back in the zone and I still have to bring the application back to the state where I was developing. This alone is at least 10 minutes lost for a minor change. JRebel deserves every single cent of its selling price.
With JRebel, I am able to see code changes more or less in real time - JEE development is a joy once more!
Every delay sucks, so whatever causes less delays rocks.