Skip to content

Commit aaea149

Browse files
committed
Add mention to Quarkus Outbox pattern post
1 parent e75c258 commit aaea149

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/posts/quarkus-dapr.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ So, what are Dapr building blocks? Essentially, building blocks are APIs accesse
3737

3838
![Diagram showing the communication between Quarkus and Dapr to use State Store and Pub/Sub](./assets/quarkus-dapr-diagram.png)
3939

40-
??? note "Note about the diagram"
40+
??? note "About the diagram"
4141

4242
The diagram above illustrates what we will implement in the following sections, using an in-memory State Store and Pub/Sub for simplicity. However, Dapr is not limited to these options and supports a wide range of state stores and messaging systems.
4343

@@ -94,7 +94,7 @@ scopes:
9494
- app2
9595
```
9696
97-
Getting State management as example, you can enable transaction outbox pattern, using the component specification:
97+
Getting State management as example, you can enable [transaction outbox pattern](./outbox-pattern-in-quarkus.md), using the component specification:
9898
9999
```yaml
100100
apiVersion: dapr.io/v1alpha1

0 commit comments

Comments
 (0)