Cloud-based integration

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Cloud-based integration is a form of systems integration delivered as a cloud service that addresses data, process, service-oriented architecture(SOA) and application integration use cases.[1]

Two cloud-based integration service models are iPaaS (Integration Platform as a Service) and dPaaS (Data Platform as a Service):

  • iPaaS is a suite of cloud services enabling customers to develop, execute and govern integration flows.[2] Under the cloud-based iPaaS integration model, customers drive the development and deployment of integrations without installing or managing any hardware or middleware.[1] The Ipaas allow small businesses to achieve integration without a big investment in skills or licensed middleware software.
  • dPaaS delivers cloud-based integration as a fully managed service.[3] Under the dPaaS model, the cloud platform provider, not the customer, manages the development and execution of integrations. dPaaS users retain transparency and control over data through data visualization tools.[4]

Emergence

Prior to the emergence of cloud computing, integration could be categorized as either internal or business to business (B2B). Internal integration requirements were serviced through an on-premises middleware platform and typically utilized a service bus to manage exchange of data between systems. B2B integration was serviced through EDI gateways or value-added network (VAN). The advent of SaaS applications created a new kind of demand which was met through cloud-based integration.[5] Since their emergence, many such services have also developed the capability to integrate legacy or on-premises applications, as well as function as EDI gateways.

Identification

While the features regarded as essential in order to classify a cloud-based integration service as such are debated, the following are commonly accepted:[1]

  • Deployed on a multi-tenant, elastic cloud infrastructure
  • Subscription model pricing (opex, not capex)
  • No software development (required connectors should already be available)
  • Users do not perform deployment or manage the platform itself
  • Presence of integration management & monitoring features

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.