Now a days a lot of buzz is going on which is better ESB on premises or iPaaS integration tool.Both has their own advantage and drawback. We need to choose based on requirement and current circumstances not blindly move on cloud.
Many organizations chose to not move everything in to the cloud because of these and other factors:
- Company policies
- Country policies
- Industry domain specific policies
- Not all functionalities/applications are available on the cloud or are not as robust as those available on-premise, etc.
There are three reasons many companies are looking at moving from BizTalk to Azure iPaaS:
- cost, consumption pricing instead of product licensing: Here there is a catch, iPasS hybrid integration cast on the basis on data transaction and size of data. So, it will be always better if there is less data transaction & light weight message. If this is not the case, then cost will be very high in adapting iPaaS integration solution.
- location of data, many companies are dealing with their consumers over the internet, so having their integration resources in Azure makes more sense. If there are several data location is on on-premises, then its will better to use BizTalk
- Infrastructure, companies are seeing the advantages of not having to maintain their own infrastructure and using Platform as a Service (PaaS) and Software as a Service (SaaS) offerings as a cost-effective alternative.
|iPaaS Integration||BizTalk Server|
|Cost, consumption pricing instead of product licensing: iPaaS will be better for light weight data transactions||iPasS hybrid integration cast on the basis on data transaction and size of data. So, it will be always better if there is less data transaction & light weight message. If this is not the case, then cost will be very high in adapting iPaaS integration solution.|
|Location of data, many companies are dealing with their consumers over the internet, so having their integration resources in Azure makes more sense.||If there are data location is on on-premises, then its will better to use BizTalk. Also, it will provide fast data transaction rather than iPaaS|
|Infrastructure, companies are seeing the advantages of not having to maintain their own infrastructure and using Platform as a Service (PaaS) and Software as a Service (SaaS) offerings as a cost-effective alternative||It will depend on what are involve in integration. If there are heavy data transactions, several data transformation, business process automation. Combination of on-premises and cloud service then its better to go with BizTalk|
|Sensitivity of your data, there is always concern with data||Everything is in organization hand|
|Security Policies for accessing cloud-based resources||Everything is in organization hand|
|Location of consumers/partners. There is some time issue with Nation level security policy||Everything is in organization hand|
Before you jump full steam into migrating from your on-premises (or cloud hosted) BizTalk to Azure iPaaS, there are a few things that you need to look at to see if the migration makes sense:
- Location of your data
- Sensitivity of your data
- Security Policies for accessing cloud-based resources
- Location of consumers/partners
Despite the innovation happening on the Azure Integration Services side, Microsoft still sees a role for BizTalk Server. It supports “hybrid” scenarios, where organizations run BizTalk Server on their own infrastructure while connecting to Microsoft’s and other providers’ services.
If you’re using a hybrid cloud environment, Organizations are using BizTalk for on-premises integrations and Azure Logic Apps for SaaS to SaaS integrations when appropriate but have the flexibility to connect both scenarios with our native adapters between both products.
Best scenario for implementation of BizTalk:
- When there is require integrating lots of Legacy System, On-premises systems
- Very high traffic among systems
- Location of data, if most of your data currently is located inside of data center
- BizTalk is designed to integrate complex IT systems and architecture
- Enterprise system like ERP, traditional CRM
- Must deal with EDI/X12 etc.
- Complex business rules in existing code for .NET
- BizTalk is very easy to integrate if the development is mainly on the Microsoft software family.
Best scenario for using iPaaS
- iPaaS is a set of integration tools delivered from a public cloud and requires no on-premises hardware or software
- Lightweight messaging and document standards (REST, JSON, etc.) used by today’s cloud apps
- iPaaS offers a more lightweight integration solution better suited for flexible and real-time applications, which are critical requirements of cloud-based services.
- It will better to use when maximum system will be on cloud, SaaS or data transfer via internet
- Organization don’t want to manage infrastructure