Clustered Deployment Patterns
- Former user (Deleted)
We can identify several patterns of a distributed deployment involving the above components. The most prominent of them are as follows.
- Store and Publisher Components in a Single Server Node
- Store Component on an External Network
- All Components in a Clustered, Internal Setup
- All Components in a Clustered Setup with an External Store
Store and Publisher Components in a Single Server Node
The diagram below depicts a minimum deployment of API Manager component nodes. This pattern is for an internal store, so the Store and Publisher components are deployed on a single server node.
Store Component on an External Network
This pattern is similar to the previous one, except that the Store component node is deployed on an external network. The diagram below depicts a minimum deployment of the store.
All Components in a Clustered, Internal Setup
This pattern extends the individual component nodes and deploys them in a cluster for high availability. Each component node can be extended up to n number of server nodes based on the deployment load. This pattern is based on a complete internal deployment where all API component nodes are deployed internally. The diagram below depicts a minimum deployment of the components.
All Components in a Clustered Setup with an External Store
This pattern is similar to the one above and also provides high availability, but it considers the use of an external store. The diagram below depicts a minimum deployment of the components.
Next, let's see how to configure these deployment patterns in Generic Configurations of the Deployment.