“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 real solution for build/deployment pain in Java EE. Good product. It just works and doesn't need a 3 hour configuration phase :)
Why isn't JRebel part of the standard Java SDK?
Everyone who has tried it has fallen in love with it.
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.
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 really an amazing tool.
Con JRebel, salvar un archivo en el IDE y ver mis cambios inmediatamente en la pagina sin tener que volver a hacer "deploy", no tiene precio.
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:)
Given the nominal cost of JRebel and the huge amounts of time it saves, I would not consider developing Java EE applications without it.
I seriously cannot understand how I used to do my job without #jrebel.
Setting up JRebel was completely painless and my questions on the support forum were answered quickly. The performance gains were immediately obvious to us, so after the evaluation period was over we decided to purchase licenses for all our developers.
Over the last 265 days JRebel prevented at least 1,209 redeploys/restarts saving me about 49 hours.