September 29, 2015
View all 2 Followers
View all 1356 Related Articles
Related Articles (1356)
FinancialForce.com, focused on building cloud based business applications on the Force.com platform, has released an API for its accounting application (i.e. The FinancialForce Accounting API). The API gives access to the entire suite of accounting tools available through the accounting platform (e.g. cash management, reporting and dashboards, ordering and billing, etc.). Although FinancialForce.com built the application with Force.com, and the target audience began with Force.com developers, the application has been integrated with many platforms and APIs (e.g. Google Apps, Basecamp, Facebook, PayPal, etc.)
In a press release on 11 March 2013, Message Bus announced that its Message Bus Platform is now available for integration via Zapier's drag and drop API integration capabilities. This is exciting news for anyone trying to create efficient integrations and workflows that make sense for business but don't come with the associated efforts, long lead times and costs that custom API work entails.
One of the big debates these days when it comes to cloud computing center around portability and interoperatbilty between providers. That is, if you build an application on Amazon's EC2 or Google's AppEngine or Force.com, or store your data on Box.net or Amazon's S3, how hard is it to port your application or move your data to another cloud provider? If you develop on a given platform, how locked-in, or not, are you? And beyond that, could developers benefit from having standardized APIs to develop to without having to learn a new model and interface each time. As you'd expect, there's no easy answer to this.