Heroku embraces enterprise Java
September 19, 2012 —
(Page 1 of 2)
Related Search Term(s): Heroku, Java, PaaS
When Salesforce.com purchased Heroku at the end of 2010, it was obvious that the two companies would cross-pollinate. Two years later, that pollination has born enterprise-ready fruit for the PaaS company that began as a quick and easy way to host Ruby applications. Today, Heroku announced a bevy of new services and product offerings that amount to a US$1,000 per-month, per-application hosting plan for enterprise Java users.
Jesper Joergensen, senior director of product management at Heroku, said that there were a few major needs enterprises had that, as a startup-focused PaaS, Heroku didn't quite understand. He said that Salesforce’s biggest change for Heroku after the acquisition was to offer the company a fresh focus on enterprise users.
Oren Teich, COO of Heroku, said that this is when “we realized there are two things we needed to provide to enterprises. One was polyglot: They all want multi-language support. But at the same time, there's a real need for what I call idiomatic support of a language. The way you look at a Ruby developer is different than the way you look at a Java developer. A Ruby developer is probably on a Mac, loves the command line, and uses no IDE. A Java developer is probably on Windows, uses Eclipse, and doesn't want a command line. It's important that you go deep into a language and understand the users.”
Joergensen comes from a Java background, and he joined the Heroku team from Salesforce proper shortly after the acquisition. Before Salesforce, he worked at BEA Systems. As such, Joergensen understands that traditional enterprise Java environment.
“We've been going into these enterprises that Salesforce is already in, and listening to them, and trying to find out where the barriers are,” he said. “Java very much defines, today, how enterprises look at what it takes to deploy a Web application. They want to move to the cloud, but what does that deployment look like in the cloud? There's been a barrier there because cloud infrastructure doesn't look like what we have on premise. There's always a set of standard components that come with a Java application. There's a SQL database, a caching tier, load balancing, a container, and scaling sessions is a classic problem from an infrastructure perspective.”