PaaS Heroku’s misleading of customers poisons the cloud
Grazed from The Register. Author: Jim Clark.
Platform-as-a-service Heroku spent two years misleading customers because it was so focused on building a new product that it didn’t bother to update old documentation – this is unacceptable. The Salesforce-owned company admitted on Wednesday that customers using its ‘Bamboo" application automation technology could have spent two years paying for a service that used different tech to that found in Heroku’s docs, and that this tech entailed poor app performance that was nearly impossible for both Heroku and Heroku analytics partner New Relic to detect.
An equivalent situation would be a logistics company announcing it had not informed customers that it had shifted from using a central dispatcher to direct its trucks, to a system where each driver had a list of all packages and had to work out the delivery order with other drivers with no central command. Moreover, that this change meant packages were not getting delivered on time and that it had no way of informing customers of the tardiness of their packages…



The Apache Software Foundation announced in late March that CloudStack is now a top-level project. This is a promotion from CloudStack’s incubator status, where it had lived after being released as open source by Citrix. This promotion provides additional encouragement to companies and developers looking to contribute to the project, because it validates the CloudStack community and demonstrates ongoing support under the Apache Software Foundation.