📄️ Glossary
|Name|Description|
📄️ Cluster Topologies
This page illustrates the architecture for setting up single-zone and multi-zone clusters.
📄️ Pod - Level Sizing
Cluster sizing recommends the number of pods of each type that are required for different Queries per Seconds (QPS).
📄️ High Availability Cluster Design
Local Edition architecture is quite flexible, and can be scaled up or down as needed. But other than TPS consideration, to achieve High Availability (HA), you need to carefully design the cluster. Container orchestrators (K8S) can take care of components failure, for example, if one Local Edition component shuts down due to some reason, they will bring another one to maintain the given number of instances if all the criteria are satisfied. But to achieve HA in case of infrastructure failure (such as node failure, zone failure, etc.) of K8S, extra planning should be done before creating cluster. HA at different levels requires different planning. The following sections provide some general guidelines to achieve HA for the Local Edition cluster to work as expected.
📄️ Cloud API Management - Local Edition Database Characteristics (added in v6.2.0)
The following table provides information about database characteristics in tethered and untethered modes. Refer to Preparing Database for more information.
📄️ Cloud API Management (Control Center) and Database Interaction (added in v6.2.0)
Table Design
📄️ Database Recommendations (added in v6.2.0)
Database Settings
🗃️ High Availability (HA) of MySQL (added in v6.2.0)
1 item
