“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
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!
We found some very interesting side-effects right away. The worst of those was some badly coded Hibernate which would generate over 700 database queries. The JSF memory footprint was a bad surprise - some beans are in the session, that shouldn’t have been there.
#IntelliJ and #JRebel combined cost less than your consultant's daily wages, but will boost his productivity x10. Why hesitate ?
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 is really an amazing tool.
Saving time with JRebel is so amazing. No more redeployments... Refactoring classes, Refresh the page and that's it! Amazing stuff!
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.
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'
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:)
I see JRebel as this "missing piece" in the whole picture where we could see Java-stack not only as a stable, well-tested environment to build applications on but also as a rapid development environment.
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.
I started using JRebel for web and server deployments on JBoss and I've been addicted ever since. It simply just works :-)