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

## 8.2 How many API Connect Clouds and Gateways 

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. 

## 8.2.1 Separate API Clouds 

There are various requirements that might lead to the creation of a new team on a separately provisioned cloud. Cloud-level separation allows for: 

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. 

## 8.2.2 Separate API Gateway Cluster 

GLYPH<SM590000> Supporting varying or conflicting non-functional requirements. 

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: 

