With applications and data rapidly moving to the cloud, businesses are continuing to focus on integration and the part it plays in a cloud solution ecosystem. While an application may be an island of functionality, the data is often necessary in other parts of the business. Integration between applications can deliver enhanced or specific functionality required by business users, but application data integration allows information to be passed from system to system, enabling the re-use of data for various purposes within the enterprise.
This focus on integration in the cloud has spurred the increasingly complex need for standards in communication, which is the purpose of developing an API. However, when a single door is created for data to pass through, that door also represents a vulnerability in the system – a vulnerability which could reveal itself in a variety of ways.
For developers, this creates a heavy reliance upon the integration framework and web solution provider – a reliance that may not deliver the benefits that a software-based integration once did.
The proliferation of mobile devices has created a firestorm of demand for Application Programming Interfaces (API) to act as data gateways between devices and services. But fire can also be a destructive force, and mis-managed APIs can hurt application performance, alienate developers and even lead to costly and damaging data breaches.
API isn’t all roses and sunshine for developers, but the appeal of silent web services integration is quite compelling – particularly if you can continue to control the data and the access.
This trend describes why Intuit pushing the IPP and killing the SDK. It may make sense for them, but does it make sense for their developer partners? For folks who saw success with the SDK, changing to the IPP changes more than just the software, it changes the dependency and relationship on Intuit’s own servers and systems.
Read about The Demise of the QuickBooks 3rd Party Developer by Chuck Vigeant; QuickBooks and Beyond