Decide on the number of gateway nodes, and install and configure them (local or remote to Cassandra).

Decide on the number of Cassandra nodes, and install and configure the Cassandra database on each node.The following general guidelines apply to configuring a Cassandra HA cluster: This configuration applies to all supported use cases (for example, API Manager and API Gateway custom KPS, OAuth, and client registry data). If one Cassandra node fails or needs to be restarted, the cluster continues to operate with the remaining two nodes. QUORUM read/write consistency to ensure that you are reading from a quorum of Cassandra nodes (two) every time.Ĭaution Eventual consistency is not supported in a production environment due to a risk of stale or missing data.In this scenario, if the node that stores the user permissions goes down, the client (API Manager) cannot login to other nodes, and the cluster becomes unavailable. Therefore, they cannot be checked, and requests to them are rejected. Without this configuration, the user permissions are not replicated to other nodes.Replication factor setting set to 3 for the system_auth and API Management keyspaces, so each node holds 100% of the data.It is not recommended to make all Cassandra nodes a seed, as they produce traffic overhead.Other nodes contact the seed node when joining the Cassandra cluster to get required cluster information, therefore you must start the seed node first.

Three Cassandra nodes (with one seed node).

To tolerate the loss of one Cassandra node and to ensure 100% data consistency, API Gateway requires at a minimum the following Cassandra cluster configuration running in a production class environment: Set up an Apache Cassandra database cluster for high availability (HA) of your API Gateway system.ħ minute read Cassandra HA in a production environment

Best pgp application cassandra