Fiorano API management architecture scales linearly, allowing the infrastructure to grow on an as-needed basis. The classification of gateway servers into environments allows scaling a natural process.
The project deployment is linked to environments rather than the physical servers which facilitates flexible deployment patterns.
Scaling
Configuring a Single Server Environment
Perhaps the simplest form of configuring an environment is to map only a single physical gateway server. Create an environment with name 'GatewayServer1' by following the steps mentioned in the Creating an Environment for Project Deployments section. Similarly, add another environment with name 'GatewayServer2'. In this example, apigateway1 and apigateway2 are added for GatewayServer1 and GatewayServer2 respectively. There is no distinction between environment and server in this case. So the IP of the server can be directly made available to the clients.
Figure 1: Adding Gateway Servers / Environments
As and when the load on the Servers increase, there are multiple ways to cope with the increased traffic which typically would involve increasing the system resources allocated to the server like memory and CPU. These processes generally incur some downtime for services. The concept of environments provide a way to scale in such scenarios without any downtime.
Adding multiple Servers to Environments
To scale with increased traffic without any downtime, a new server instance can be started. Then, from the dashboard, add the server to the environment on which the increased activity is observed.
Figure 2: Adding new server to the environment with more activity