Marriage of Onpremises and Cloud Software - Problems and concerns

•Social Media or Cloud Adapters break too often

•Non-mature cloud vendors changes an API or interface or authentication very quickly with/without informing the data integrators or the DI vendors are not ready to make the changes in that time frame.
e.g.. Microsoft Dynamics CRM Live authentication, Facebook API changes,Twitter API v1 obsolescence.

•Delay in delivering fixes and pains in implementing fixes

•A change in the cloud application back-end system or the API or metadata would require a patch to be shipped pretty fast and installed quickly to continue data integration. Usually, the overheads of shipping such an on-premise installers are in days instead of hours. The customer base could be thousands.

•Older versions of  adapters does not support newer cloud features

•Older versions of cloud adapters were built and certified some time back. Typically R&D does not have the bandwidth to certify the old adapter versions everytime when the cloud vendor makes a change.

•Reduced synergy between the  Cloud and on-premise product teams

•Typically the inhouse cloud product teams does not use the latest on-premise software versions or vice versa (incase the cloud software is a flavor of the on-premise on deployment.