GLYPH<SM590000> Gateway Server would continue to process existing API traffic but will not be able to  support: – API publications – Onboarding new applications or subscriptions – Token revocation – Rate limiting (quota enforcement) GLYPH<SM590000> Node failure:  Single node failure will not have any impact, but if two nodes fail then  quorum would be lost and the components will behave as described earlier.  GLYPH<SM590000> Data center failure : Application will not be available. GLYPH<SM590000> Simple single Kubernetes cluster setup. GLYPH<SM590000> Latency of < 30 ms is required between the nodes. Now that we have described API Connect components and the quorum concepts, let’s cover  few sample topologies.  We will discuss some common topologies and assess their high availability capability.  Figure 8-10 shows the single cluster, single location setup. This is the simplest API Connect high availability topology. Assuming that the components  are placed as shown in Figure 8-10, let’s evaluate this solution against common failures: Advantages of single cluster setup are as follows: Concerns of single cluster setup are as follows: 556  Accelerating Modernization with Agile Integration Figure 8-10 Single cluster, single location topology Sample topologies Single cluster, single location setup