|
|
|
|
|
by pan69
1496 days ago
|
|
Isn't the elephant in the room then; why did Salesforce buy Heroku? I mean: > From a strategy POV, for better or worse, Salesforce is not particularly focused on integrated acquired products > I heard revenue and margins weren't sustainable prior to the acquisition What was the point of the aquisition? To let it die? |
|
After Apex was introduced in 2006, Salesforce suffered criticism (misplaced, IMHO) over the fact that it was proprietary. In 2009 it did a partnership with VMware to create a Java-as-a-service proto-PaaS so business logic could be written in Java instead of Apex. This service (VMforce) never worked for a variety of reasons, leaving Salesforce to look for an alternative -- so in early 2011 they bought Heroku. Thats why the first thing Heroku did post acquisition was build Java support.
Turns out this wasn't a great product idea to start (the limitations of externalizing business logic, especially at that time, weren't worth the effort), so the strategic reason for the acquisition was no longer relevant. Years later there were successful integrations that had different value propositions, although those suffered from the constraints described above.