You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far we've built an object handling load balancing, routing, and content manipulation across multiple sites.
11
-
XC refers to these as "load balancers" but it's really the holistic representation of a service whose components live across a distributed network.
12
-
Our object is a simplified representation that does not include WAAP, API Protection, or service policies.
13
-
XC is incredibly flexible in defining where that object is advertised.
10
+
The configuration built so far handles load balancing, routing, and content manipulation.
11
+
XC refers to this object as a "load balancer" -- but it's really the holistic representation of an application whose service endpoints live across the distributed network.
12
+
The object is simple -- it doesn't yet include configuration for WAAP, API protection, or a service policy.
13
+
14
+
What seperate XC from traditional ADCs is the flexibility of defining <strong>where the object is advertised</strong>.
<aclass="btn btn-primary"data-bs-toggle="collapse"href="#multiCollapseExample1"role="button"aria-expanded="false"aria-controls="multiCollapseExample1">Why did that work?</a>
0 commit comments