Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit7408620

Browse files
committed
Update image filenames
1 parenta947370 commit7408620

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed

‎circuit-breaker/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ remote calls.
4949

5050
The service architecture is as follows:
5151

52-
![alt text](./etc/ServiceDiagram.PNG"Service Diagram")
52+
![alt text](./etc/ServiceDiagram.png"Service Diagram")
5353

5454
In terms of code, the end user application is:
5555

@@ -292,7 +292,7 @@ public class DefaultCircuitBreaker implements CircuitBreaker {
292292
How does the above pattern prevent failures? Let's understand via this finite state machine
293293
implemented by it.
294294

295-
![alt text](./etc/StateDiagram.PNG"State Diagram")
295+
![alt text](./etc/StateDiagram.png"State Diagram")
296296

297297
- We initialize the Circuit Breaker object with certain parameters:`timeout`,`failureThreshold` and`retryTimePeriod` which help determine how resilient the API is.
298298
- Initially, we are in the`closed` state and nos remote calls to the API have occurred.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp