A more fundamental change is the continued focus on enabling container-based deployment  of the on-premises runtime. Containerization is not mandatory for v11 of IBM App Connect.  You can upgrade the runtime only, retaining your existing Integration Node/Integration Server  topology, and benefit from many fundamental enhancements in the new version. However,  containerization and the associated move to a more cloud-native approach has many  advantages. The advantages include simpler deployment build pipeline, isolation/decoupling  between integrations, consistency across environments, portability, standardized  administration and monitoring, and common capabilities to enable non-functional  characteristics such as elastic scaling and high availability and self-healing.  Several other benefits of cloud native deployment are already discussed in 7.1.2, “Adoption  path options” on page 434. Another important aspect to consider while migrating to  containerized environment is the grouping criteria for integrations. Section 7.2, “Splitting up  the ESB: Grouping integrations in a containerized environment” on page 441 describes  grouping criteria that you can use to decide which integrations could/should stay together,  and which ones must be separated from one another. The architecture change in IBM App Connect V11 that introduces independent integration  server has brought in several changes to the runtime directory structure. Therefore, it is  important to understand how the runtime resources and configuration in IIB maps to IBM App  Connect V11. For example, the registry, resource manager configuration, integration  node/server configuration, configurable services in IIB are now defined in  server.conf.yaml  file. Policies replace configurable services in IBM App Connect. The deployed artifacts are  stored under the  run  directory. Figure 7-47 on page 493 shows how the runtime work directory structure of IIB maps to IBM  App Connect.  Runtime work directory structure changes in IBM App Connect V11 In the subsequent sections of this chapter we primarily focus on the containerization aspects  of IBM App Connect and discuss configuration requirements for some of the commonly used  endpoints in integration flows.  Figure 7-47 Resource mapping between IIB and IBM App Connect  Chapter 7. Field notes on modernization for application integration  493