content_image/1006421.jpg
## 7.1 IBM App Connect adoption paths 

IBM App Connect V11 combines the existing, industry-trusted IBM Integration Bus (IIB) software with new cloud based composition capabilities, including connectors to a host of well-known SaaS applications. However, a more fundamental change is the continued focus on enabling container-based deployment of the on-premises software runtime. But V11 does not mandate a move to containers. Customers can continue deploying workloads in the more centralized ESB pattern if that is their preference. In this section, we focus on deployment options for the on-premises software, comparing the traditional centralized ESB topology with the alternative containerized deployment in order to understand the pros and cons of each path. 

## 7.1.1 Agile integration 

Figure 7-1 summarizes the progressive phases of integration modernization defined by agile integration. 

<img src='content_image/1006421.jpg'>

Agile integration has the potential to dramatically improve the velocity at which connectivity is delivered, and the discrete resilience and elastic scalability of isolated integrations. Much of this is achieved initially by moving to a more fine-grained deployment of the integrations themselves making it possible to change integrations more independently. After integrations can be deployed independently, this lays the foundations for decentralized ownership whereby the ownership of the integrations moves from a central integration specialist team out to the application teams. Enterprises vary in how far down this road they need to travel and at what pace. 

## 7.1.2 Adoption path options 

So, what does this mean for users who have been running workloads on previous versions of IBM Integration Bus? When we upgrade to IBM App Connect, how can we best prepare ourselves to leverage agile integration benefits? 

