Identifying Rogue proxy to minimize the environment impact

Hi All,

Within our organization, we have multiple API proxy build in our Apigee ( version 1.6.9) cloud environment which are for different divisions. All API Proxy share the same cloud space.

We are trying to avoid a scenario where there is a Rogue proxy being build, or a proxy contains improper implementation, which can affect the other proxy or the cloud environment itself or performance of the environment.

Are there any manually checks we can perform prior deploying the proxy to PROD so that we can minimize (or avoid) the situation where the whole environment is unavailable? Are there any specific Antipatterns in proxy design we can check?

Thanks in advance,

Pari

0 1 80

1 REPLY 1