| ID | Title | Description |
|---|---|---|
| CCC.LB.CP01 | Static Load Balancing | Employ load balancing algorithms that follow fixed rules, independent of the current server state. |
| CCC.LB.CP02 | Dynamic Load Balancing | Employ load balancing algorithms that consider the current state of servers before distributing traffic. Load balancer adjusts traffic distribution in real-time based on the current server health, resource utilization, and traffic conditions. |
| CCC.LB.CP03 | Layer 7 Routing | Providing distribution of incoming traffic based on the application layer or layer 7 (on ISO model) information. Some of the supported protocols on layer 7 are HTTP, HTTPS, HTTP/2, gRPC, and WebSockets. |
| CCC.LB.CP04 | Layer 4 Routing | Providing distribution of incoming traffic based on the transport layer or layer 4 (on ISO model) information. It uses the combination of IP addresses and TCP/UDP port to distribute incoming traffic rather than inspecting the actual content of the packets. |
| CCC.LB.CP05 | URL-Based Routing | Direct incoming requests to different backend resources based on the content of the request URL. |
| CCC.LB.CP06 | HTTP Header-Based Routing | Direct incoming requests to different backend resources based on the values of HTTP headers. |
| CCC.LB.CP07 | WebSocket Support | Ability to support web socket communication. |
| CCC.LB.CP08 | Dual-stack Load Balancing | Ability to support traffic originated from both IPv4 and IPv6. |
| CCC.LB.CP09 | Load Balancer Autoscaling | Ability for the load balancer to dynamically adjust its capacity in response to fluctuations in incoming traffic. |
| CCC.LB.CP10 | Target Autoscaling | Ability for the load balancer to trigger scaling actions of the backend instances (targets) to handle fluctuations in incoming traffic. |
| CCC.LB.CP11 | SSL/TLS Termination | Process of decrypting SSL or TLS encrypted traffic at the load balancer level rather than at the backend servers. This allows the load balancer to offload the decryption task from the backend servers. |
| CCC.LB.CP12 | Target Health Checks | Ability to continuously perform health checks on backend backend targets in form of checking the response to HTTP request, TCP connection or checking other application-specific parameter |
| CCC.LB.CP13 | Health Checks-based Target Removal | If the health check detects that a backend target is unhealthy the load balancer will remove that unhealthy target from its list of available backend instances. This ensures that traffic is no longer routed to the unhealthy target. |
| CCC.LB.CP14 | Retries | Ability to retry delivery of failed requests to targets. The conditions under which the load balancer retries, how long to wait before retrying, and the maximum number of retries permitted are configurable. |
| CCC.LB.CP15 | Session Affinity | Can configure subsequent requests from an initial client to be passed to the same target. |
| CCC.LB.CP16 | URL Redirects | Redirect incoming traffic to a different URL or location. |
| CCC.LB.CP17 | URL Rewrites | Rewrite URL paths before forwarding them to backend services. |
| CCC.LB.CP18 | Custom Response | Ability to configure specific HTTP responses to be returned by the load balancer under defined conditions. |
| CCC.LB.CP19 | Request and Response Header Transformations | Ability to modify HTTP headers of both incoming requests and outgoing responses. |
| CCC.LB.CP20 | Traffic Splitting / Weighted Routing | Can distribute incoming traffic across multiple backend resources based on predefined weights or percentages (e.g., for canary deployments, A/B testing, blue-green deployments, or gradual traffic migrations). |
| CCC.LB.CP21 | Traffic Mirroring | Can duplicate incoming network traffic and send it to a secondary destination for monitoring, analysis, or testing purposes. |
| CCC.LB.CP22 | Rate Limiting / Throttling | Ability to limit the number of requests per second per client. This ensures that no single client or user overloads the backend servers, distributing requests fairly across multiple instances. |
| CCC.LB.CP23 | Firewall Integration | Ability to seamlessly integrate with firewall services to ensure only legitimate and secure traffic reaches backend servers, blocking malicious requests. |
Networking / Loadbalancer
Capabilities
Version: