HTTP/1.1 200 5.09 secs: 75 bytes ==> GET / HTTP/1.1 200 0.02 secs: 74 bytes ==> GET / HTTP/1.1 200 0.03 secs: 74 bytes ==> GET / HTTP/1.1 200 0.02 secs: 74 bytes ==> GET / HTTP/1.1 200 5.14 secs: 75 bytes ==> GET / HTTP/1.1 200 0.02 secs: 74 bytes ==> GET / HTTP/1.1 200 0.02 secs: 74 bytes ==> GET / HTTP/1.1 200 0.03 secs: 74 bytes ==> GET / HTTP/1.1 200 0.01 secs: 74 bytes ==> GET / HTTP/1.1 200 5.03 secs: 75 bytes ==> GET / HTTP/1.1 200 5.05 secs: 75 bytes ==> GET / HTTP/1.1 200 5.01 secs: 75 bytes ==> GET / . . Transactions: 40 hits Availability: 100.00 % Elapsed time: 25.17 secs Data transferred: 0.00 MB Response time: 2.03 secs Transaction rate: 1.59 trans/sec Throughput: 0.00 MB/sec Concurrency: 3.22 Successful transactions: 40 Failed transactions: 0 Longest transaction: 5.14 root@scamp1:~/istio_lab/cb# cat destination_rule_cb.yaml  apiVersion: networking.istio.io/v1alpha3 kind: DestinationRule metadata: name: catalog spec: host: catalog trafficPolicy: connectionPool: http: http1MaxPendingRequests: 1 maxRequestsPerConnection: 1 tcp: maxConnections: 1 outlierDetection: baseEjectionTime: 120.000s consecutiveErrors: 1 interval: 1.000s maxEjectionPercent: 100 As we can see in Example 9-30 on page 308, all requests to our system were successful,  but it took some time to complete the test, as the v2 instance of catalog was a slow  performer. But suppose that in a production system this 5 second delay was caused by too  many concurrent requests to the same instance. This might cause cascade failures in your  system.  4. Now, add a circuit breaker that will open whenever there is more than one request that is  handled by the catalog microservice. See Example 9-31. Example 9-31 Add a circuit breaker Chapter 9. Service mesh implementation using Istio  309