Would iPaaS replace ESB?

Web Services and Enterprise Service Bus

Since the beginning of this century ,web services became the popular glue for  integration between organization internal systems as well as external service providers.  Now web services became the primary methods of integrate an IT infrastructure. 

The enterprise service bus, known as the ESB, provided the ability to consolidate services through a centralized entity.Everything was connected directly to the enterprise service bus and the ESB routed data as necessary. While this provided increased flexibility and scalability, it also slowed down communication times and increased overhead.

Wonder what is the fastest ESB, check this out..

Integration-Platform-as-a-Service (iPaaS)

Integration-platform-as-a-service is the latest god in the systems integration evolution. It allows a organization to integrate their entire IT system through a service platform architecture. Rather than hosting integration platform in-house, iPaaS delegates all the complexity to a 3rd party vendor. Such architecture provides immediate access to the latest product features, decreases maintenance overhead and ensures extended resources availability. iPaaS is the natural extension of the popularity of SaaS deployment, allowing SaaS solutions to be integrated into a singular platform through a comprehensive and consolidated system.

 would it ?

These 2 concepts are different and serve a different purpose.
While you can integrate any back-office application with iPaas, you will face constraints and issues such as:
– how do i expose securely the legacy applications i want to integrate with?
– what would be the latency if many calls have to be done from the iPaas to the back-office (assuming the iPaas is used for Service Orchestration, or else it cannot be compared with an ESB)?

So, iPaas should be used for applications that require cloud-to-cloud integration, and very few back-office calls, while ESB is to be used for on-premise applications integration and service orchestration. Both products can be used in many projects where the ESB is used to expose fine-grained internal services that are then consumed by cloud applications through the iPaas.


One thought on “Would iPaaS replace ESB?

  1. So with your explanation, iPaas is seems on top of on typical ESBs. ESBs to do expose fine grained legacy services which are then consumed by iPaas apps and it can be a good use case too. But it can have drawbacks such as performance impact when all traffic goes though iPaas (I meant a user who migrate from a legacy ESB to a ESB+iPaas). In that case, you would find WSO2 ESB interesting where it enables you to have cloud-cloud integrations using quite a few inbuilt connector constructs. We only need to have few lines configuration and we are almost done. I found it very useful in that sense. With it’s latest performance numbers, WSO2 ESB resides on top. You can refer http://wso2.com/products/enterprise-service-bus/ for more details.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s