Skip to content

Commit f337107

Browse files
committed
Added sequence diagrams
1 parent 5132f81 commit f337107

File tree

3 files changed

+10
-1
lines changed

3 files changed

+10
-1
lines changed

graph/patterns/LRO.gif

14.2 KB
Loading

graph/patterns/RELO.gif

11.3 KB
Loading

graph/patterns/longRunningOperations.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,20 @@ There are two flavors of this solution:
2727
the operation. This pattern is often called RELO (Resource based
2828
Long-running Operation).
2929
//image
30+
<!-- markdownlint-disable MD033 -->
31+
<p align="center">
32+
<img src="RELO.gif" alt="The status monitor LRO flow"/>
33+
</p>
34+
<!-- markdownlint-enable MD033 -->
3035
2. The returned resource is a new API resource called 'Stepwise Operation' and
3136
is created to track the status. This LRO solution is similar to the concept
3237
of Promises or Futures in other programming languages.
3338
//image
34-
39+
<!-- markdownlint-disable MD033 -->
40+
<p align="center">
41+
<img src="LRO.gif" alt="The status monitor LRO flow"/>
42+
</p>
43+
<!-- markdownlint-enable MD033 -->
3544
RELO pattern is the preferred pattern for long running operations and should be
3645
used wherever possible. The pattern avoids complexity and consistent resource
3746
presentation makes things simpler for our users and tooling chain.

0 commit comments

Comments
 (0)