Figure 8-6 Build new API Connect Cloud  8.2 How many API Connect Clouds and Gateways 8.2.1 Separate API Clouds 8.2.2 Separate API Gateway Cluster There are various requirements that might lead to the creation of a new channel for API  traffic. Each new DataPower Service in the Cloud Manager relates to a new gateway domain.  That means you have isolation of traffic to the cluster of gateways that this configuration is  pushed to. Gateway separation allows for: Determining when to create new API Connect Clouds and Gateway clusters is a separate  consideration to determining when to scale or when to consider multi cloud deployments.  Organizations should consider a number of factors from impact of cloud upgrades, logging,  availability through to the level of coupling between teams.  There are various requirements that might lead to the creation of a new team on a separately  provisioned cloud. Cloud-level separation allows for: Chapter 8. Field notes on modernization for API lifecycle  547 GLYPH<SM590000> Decoupling of platform upgrade requirements across API Provider teams. GLYPH<SM590000> Separation of Cloud management concerns, which might include funding, management  team skills and management team capacity. GLYPH<SM590000> Separation of logging and analytics between teams. GLYPH<SM590000> Varying security requirements of API Provider teams, which might mean overly restrictive  procedures and protocols. GLYPH<SM590000> Supporting varying or conflicting non-functional requirements. API Connect on any Cloud Cloud APIs Customer Managed  API Connect On-premises Internal APIs Customer Managed  API Connect On-premises External APIs (Open APIs or Protected Partner APIs) API Gateway Target  Internal APIs API Gateway Target Enterprise  Services / SoR API Gateway Target Cloud  Services / Target  Internal APIs <<Private Internal Zone >> <<Secure Zone >> <<Public Zone >> API Developers (Employees) API Developers (Third Party Communities) API Developers (Employees)