From 7408620a71cb4bc0d8ba81b7f403a4bcfe17fb8e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ilkka=20Sepp=C3=A4l=C3=A4?= Date: Sat, 30 Jan 2021 14:44:41 +0200 Subject: [PATCH] Update image filenames --- circuit-breaker/README.md | 4 ++-- .../etc/{ServiceDiagram.PNG => ServiceDiagram.png} | Bin .../etc/{StateDiagram.PNG => StateDiagram.png} | Bin 3 files changed, 2 insertions(+), 2 deletions(-) rename circuit-breaker/etc/{ServiceDiagram.PNG => ServiceDiagram.png} (100%) rename circuit-breaker/etc/{StateDiagram.PNG => StateDiagram.png} (100%) diff --git a/circuit-breaker/README.md b/circuit-breaker/README.md index f1792cb24..b3a360b33 100644 --- a/circuit-breaker/README.md +++ b/circuit-breaker/README.md @@ -49,7 +49,7 @@ remote calls. The service architecture is as follows: -![alt text](./etc/ServiceDiagram.PNG "Service Diagram") +![alt text](./etc/ServiceDiagram.png "Service Diagram") In terms of code, the end user application is: @@ -292,7 +292,7 @@ public class DefaultCircuitBreaker implements CircuitBreaker { How does the above pattern prevent failures? Let's understand via this finite state machine implemented by it. -![alt text](./etc/StateDiagram.PNG "State Diagram") +![alt text](./etc/StateDiagram.png "State Diagram") - We initialize the Circuit Breaker object with certain parameters: `timeout`, `failureThreshold` and `retryTimePeriod` which help determine how resilient the API is. - Initially, we are in the `closed` state and nos remote calls to the API have occurred. diff --git a/circuit-breaker/etc/ServiceDiagram.PNG b/circuit-breaker/etc/ServiceDiagram.png similarity index 100% rename from circuit-breaker/etc/ServiceDiagram.PNG rename to circuit-breaker/etc/ServiceDiagram.png diff --git a/circuit-breaker/etc/StateDiagram.PNG b/circuit-breaker/etc/StateDiagram.png similarity index 100% rename from circuit-breaker/etc/StateDiagram.PNG rename to circuit-breaker/etc/StateDiagram.png