I came into the office this morning to see a tweet that stopped me in my tracks. Salesforce.com is acquiring Heroku for $212m. In cash! Beyond the obvious bubbliciousness of the deal was a cold hard truth about the once and future kingmakers – developers.
You see I didn’t first hear about Heroku from a marketing exec, or a PR person, or an analyst relations professional, I heard it from Tom Insam, a super-productive developer I was co-working with a little while before Dopplr was acquired by Nokia and airlifted to Berlin. This was very much a Silicon Roundabout story. Tom was all excited about Heroku because he could write code in Ruby on Rails and just deploy it to a server in the sky without needing to consider any implementation or operational details or capacity planning, or anything much. Completely situational. Heroku was basically Rails on a billing engine.
Which brings us to Salesforce.com – which is basically a billing engine across a bynch of servers with some salesforce automation on the side. Obviously Salesforce is a lot more than that, but unlike many other players they always clearly understood that job one in utility computing was billing. Heroku – the same. Salesforce avoids IT to sell to the business, while Heroku avoids IT to sell to developers. The two firms definitely have something in common. While Salesforce has done an oustanding job selling to line of business people, its direct outreach to developers through its Force.com PaaS platform and “Java-like” APEX language has been disappointing so far. Big Difference then- APEX is “Java-like”. Heroku is Rails.
Another thing Heroku potentially brings is some volume. Salesforce needs to track Amazon economics as a cloud provider, and Heroku runs on Amazon Web Services…. for now.
What about Heroku – I can’t see the obvious evidence for a $212m evaluation in terms of customer success- although Best Buy is a nice name to pick up – but Salesforce is certainly playing an interesting game. Consider that Rails developers don’t much care what the database is, really (beyond MySQL and SQLite). But purchasers want assurance, and salesforce.com just introduced database.com as a backend it claims was designed for multitenancy – with salesforce’s 25bn transactions per quarter as a proof point for scale. So could database.com be the backend for Heroku? Why not? Lets developers develop, and business people pay for Quality of Service. Seems reasonable. Of course most apps will be situational and non-relational.
I don’t want to get carried away, and I haven’t even spoken to the parties involved yet, but…
(Read the full article @ James Governor's Monkchips)