Integration Platform as a Service (iPaaS) evolved some 5 years ago in response to the requirement of companies to integrate a cloud-based service that addresses data, processes, service oriented architecture (SOA) and other application use cases into existing company systems, but using a cloud service model. This allows companies to use a suite of cloud based models to develop, execute and govern integration flows. customers typically do not have to install or manage any hardware or middleware, particularly useful for SMEs.
As I recall, Gartner were the first to come out with an iPaaS reference model, which allows users to easily compare offerings from different service providers.
The main strengths of iPaaS are the ease of implementation, the lack of investment needed in new infrastructure, the lack of a requirement to manage additional hardware or middleware, and that fact that it is paid on an accounting friendly pay as you go basis, ie Opex instead of Capex.
The limitations of iPaaS are the same as for the cloud generally. You are running on someone else's hardware, you may suffer from vendor lock-in, and of course all the usual cloud security, privacy, governance and risk issues will also apply. Clearly, the super secure corporate firewall will also not stretch to protect your iPaaS end, and the strength of the service level agreement will determine your fate to a large extent.
I have loaded some lists of references which address all the usual cloud issues, such as cloud security, cloud privacy, cloud accountability, cloud governance, and cloud risk.
Hello Bob , Thanks for sharing your thoughts. I do not see the lists of references which address all the usual cloud issues, such as cloud security, cloud privacy, cloud accountability, cloud governance, and cloud risk. Can you please send across to me. Thanks . Truly appreciated your time