In the previous post, we learnt about Azure Data Factory Integration Runtime. In this post, we will discuss Integration Runtime Types. There are three types of Integration Runtime. Microsoft provides the table and illustration below to better understand the usage scenarios of different integration runtimes:
|Integration Runtime||Public network||Private network|
|1||Azure||Data Flow, Data movement, Activity Dispatch|
|2||Self-hosted||Data movement, Activity Dispatch||Data movement, Activity dispatch|
|3||Azure-SSIS||SSIS package execution||SSIS package execution|
As we can see from the above diagram, with the Azure Integration runtime, we can run data flows , perform copy activity between various data stores in Azure and dispatch transform activity for various data stores in Azure. Azure Integration runtime can be used while connecting to data stores and compute services with public access endpoints.
Self-hosted integration runtime can be used to run a copy activity between cloud data stores and a data store in an on-prem private network behind a firewall or a Virtual Private Network (VPN).
Azure-SSIS Integration Runtime enables users to run SSIS packages natively within the Azure environment i.e. without making any changes. Azure-SSIS integration Runtime can be either provisioned in the public cloud or in a private network (VPN). With Azure-SSIS Integration runtime, Microsoft provides users the flexibility to choose either Azure data factory pipelines or use existing SSIS packages.