“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 the 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
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.
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.
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!
JRebel has transformed a nightmarish 10-minute modify, compile and debug cycle to a matter of seconds. Thanks for giving me back my sanity.
Since introducing JRebel to our Java development teams, we have not only seen a 30% increase productivity, but also a marked decrease in service requests due to software faults. Our teams can now focus 100% of their attention on development without being hindered by the J2EE cycle Build and Redeploy steps.
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!
JRebel is a blast! After the 30-day evaluation version expired, I found it hard to code anymore :-) It was very frustrating developing the old way without JRebel. Thank you very much for this wonderful piece of software!
With JRebel, I am able to see code changes more or less in real time - JEE development is a joy once more!
Life without JRebel is no fun...
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.
I like the way [JRebel monitors] the file system for changes and smartly reloads Java changes into Hot Swap/Hot code memory. It just eliminated by build time during development by 90%.
I'm afraid our developers might go for a strike if we say to them, ‘Hey, we're not going to use JRebel anymore.