Scaling up API Gateway

About this task

You must add a new API Gateway node to scale up API Gateway and handle the spike.

To scale up API Gateway,
  1. You can scale up API Gateway by simply adding a new API Gateway node to the existing cluster.

    For information on adding nodes to a cluster, see API Gateway Cluster Configuration.

  2. Add the node to Load balancer for the traffic to be distributed across the nodes.
    Note: Ensure that the new API Gateway node has same configurations as other nodes in the cluster.

    API Gateway is scaled up, and the transactions are now distributed among the nodes.

Scaling up API Gateway in a Reverse Invoke setup

About this task

The procedure is same as the one described above.

To scale up API Gateway in a Reverse Invoke setup, you can perform any of the following:
  • Add a new node in the Green zone.

    Note: If the portClusteringEnabled setting is disabled, then you need to create internal ports in the new node to connect to the registration ports of all the API Gateway nodes in the DMZ.
  • Add a new node in the DMZ zone. After bringing up the new node to the DMZ, ensure that you
    • Explicitly establish connections from all nodes in the green zone to the new node that you added to the DMZ zone. This can be done by adding Internal port in the servers in the green zone to connect to the newly created API Gateway in the DMZ zone.
    • Specify same configurations in the new node as other nodes in the DMZ zone.

      You can use the Port Configuration REST API to automate the port settings and allow the Load balancer to add the new node.

Note: API Gateway instances running in the DMZ do not need to be clustered.