Integrating Applications, Cloud Services, and Data
As you learned in the first chapter, one of the main objectives of the ESB design is to facilitate various types of integration scenarios. Integration middleware such as ESBs facilitate the key features such as communication, mediation, orchestration, transformation, QoS, security, monitoring, administration and management to cater to these disparate integration needs. At the time when the ESB is emerging as an integration technology, the primary integration requirement was to support integrations of on-premise systems and services. However, with the proliferation of APIs, mobile devices and Software as a Service (SaaS), the ESBs have to support a much broader range of integration scenarios, ranging from conventional integrations to integration of cloud services and APIs. In addition to the types of integrations that ESB supports, the integration runtime could also be a cloud service. That means you can develop, deploy, and run your integration scenarios in the cloud. This is known as Integration Platform as a Server (iPaaS).