April 18, 2017 Leave a comment
As SaaS adoption continue to increase in organisations of any size, it’s only expected that different cloud vendors will stretch their cloud capabilities to try and increasing their SaaS/PaaS/IaaS footprints. This is particularly true for iPaaS related capabilities, as it seems that every cloud vendor has its own related offering and they push it really hard even if it doesn’t really satisfy the majority of integration needs.
The challenge is though, that organisations that don’t carefully elaborate a cloud integration strategy and think this through, will almost certainly end up implementing point solutions using whichever iPaaS capability is available for the individual project. This not only results in vendor lock-in but also increases the complexity and cost of integration.
To avoid this, first step is to of course create a well thought cloud integration strategy however with a clear objective in mind. This should be delivering a platform capable of supporting all integration needs (cloud-to-cloud, cloud-to-on-premise) in a seamless and consistent fashion without redundant infrastructures and capabilities. The concept should be something like this:
However the devil is in the detail, or so it goes.
One of the key reason vendor lock-in occurs is simply because of misinformation. From my point of view, SaaS integration is all about connectivity. So without properly understanding 1) what are the connectivity requirements and 2) what platform best fits these connectivity needs in the short and long term, there is high probability that a solution will not be the right one (may be it will solve the short-term needs, but in the long-run it will probably add more complexity, cost hence risk). Read the complete article here.
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.