Micro gateway deployment into Data Centre question,Should a single instance of micro gateway be deployed (ignoring load balancing) to our data centre to manage ALL internal APIs or multiple instances that manage smaller collections of API??

[#1]

Should there be a single instance of Microgateway in our Data Centre to manage ALL our internal API (ignoring load balancing) OR should there be lots of instance that only manage smaller sets of APIs?

,

[Former Community Member]

Great question @Jim Jeffery!

At the moment, Microgateway downloads all proxy information in an environment (proxy names that match edgemicro_*). Therefore the default behaviour is for a group/cluster/set of MGs to proxy all the APIs in an environment (Edge environment).

Having said that, it is perfectly valid to use many MGs where each MG proxies a smaller set of APIs. There are a number of factors to decide which pattern one would choose.

To name a few:

1) Risk: If an MG went down and you want the scope of impact to be small, then choose pattern 2.

2) If the cost of operations/maintenance is high (since you have to manage a number of instances), then choose pattern 1. Automation tools help mitigate some of these concerns.

3) Use pattern 2 if you have a diverse set of security standards/protocols for the APIs.

4) Pattern 2 might be good if you are running inside a PaaS like Cloudfoundry.

I don't think there is a right or wrong answer. Both are valid patterns.