Today, most companies are still overwhelmingly on-premise. However, enterprises are turning more and more to the cloud in an effort to reduce the total cost of ownership (TCO) of IT architectures.
Many hope to offload non-value adding processes and applications to the cloud, whilst others are looking to migrate fully to the cloud as part of their digital transformation journey. For SaaS applications to provide real value to businesses however, they need to integrate with other SaaS or on-premise applications in order to prevent the creation of data silos.
During the first wave of SaaS implementations, lines of business have typically introduced SaaS applications without regard for the overall IT strategy. Equally, they have built their own point-to-point integrations with other applications. This results in a non-architected integration landscape which is difficult to maintain and build upon.
In such scenarios, different and often incompatible standards and software are used to provide data integration, meaning that the cost of ownership has actually increased and cross divisional integration is more complex than ever. Security holes can also result in potential risks to organizations.
This piecemeal approach leads to a mass of point-to-point integrations done haphazardly and without real thought to common standards, community management, security, scalability, visibility or agility. Furthermore, because integration is point to point, companies face real difficulties upgrading when endpoints change.
Many enterprises that attempt cloud integrations end up in this state, which is why more than half of SaaS applications fail to live up to expectations. The cloud introduces a whole new dimension of complexity including:
§ IT is no longer fully central and controlled. Cloud applications do not run in an organization’s data center, and availability, reliability, security policies etc. are governed by the SaaS vendor.
§ Tooling is often inconsistent. Cloud providers may provide unique integration toolkits and APIs. An integration tool from one vendor may not be compatible with another cloud vendor. As the number of cloud providers increase, so does the number of integration toolkits. This can lead to a spaghetti of complex integrations between various SaaS and on-premise applications. Read the complete article here.
SOA & BPM Partner Community
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog 
Twitter 
LinkedIn ![image[7][2][2][2]](https://paascommunity.com/wp-content/uploads/2013/04/image7222.png?w=20&h=20 "image[7][2][2][2]")
Facebook ![clip_image002[8][4][2][2][2]](https://paascommunity.com/wp-content/uploads/2013/04/clip_image00284222.jpg?w=26&h=23 "clip_image002[8][4][2][2][2]")
Wiki
Technorati Tags:
Andrew Bell,
Cloud integration,
ICS,
Integration Cloud Service,
Cloud,
PaaS,
SOA Community,
Oracle SOA,
Oracle BPM,
OPN,
Jürgen Kress
I have just published my first OTN Tech Article where I present a use case that demonstrates how Oracle Process Cloud Service (Oracle PCS), Oracle Mobile Cloud Service (Oracle MCS) and Oracle Mobile Application Framework (Oracle MAF) can be use together to expose an Oracle PCS process instance as a web service and consume it 
from an external system, web application or mobile application. 
"Oracle Mobile Cloud Service is Oracle’s Mobile Backend as a Service (MBaaS) and enables companies to create and deploy scalable, robust, and secure mobile applications quickly and easily."
