Skip to content

Commit 8a6587c

Browse files
committed
docs: add architecture diagram showing Java SDK interaction with Dapr runtime CORRECTION (close #<915>)
1 parent 807c953 commit 8a6587c

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

README.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,22 +13,27 @@ This is the Dapr SDK for Java, including the following features:
1313

1414
## Getting Started
1515

16+
Va, te paso un snippet ajustado tomando la idea de #897 pero siguiendo la recomendación de la review (generalizar y enlazar docs):
17+
18+
1619
### Architecture Overview
1720

1821
The diagram below shows how a Java application interacts with the Dapr runtime through the Java SDK:
1922

2023
```mermaid
2124
flowchart LR
2225
A[End User Application] -->|HTTP or gRPC| B[Dapr Java SDK]
23-
B -->|API calls| C[Dapr Sidecar]
24-
C -->|State Store, Pub/Sub, Service Invocation, Bindings, Actors, Workflows| D[External Components]
25-
C --> A
26+
B -->|Dapr API calls| C[Dapr Sidecar]
27+
C -->|Components| D[State Stores, Pub/Sub, Services, etc.]
28+
29+
%% Optional grouping for clarity
30+
subgraph R[Dapr Runtime]
31+
C
32+
D
33+
end
2634
```
2735

28-
* The application creates a Dapr client (HTTP or gRPC).
29-
* The SDK routes API calls (state, pub/sub, service invocation, bindings, actors, workflows).
30-
* The Dapr sidecar manages communication with external components and returns responses to the app.
31-
36+
For the full list of available APIs, see the [Dapr API reference](https://docs.dapr.io/reference/api/).
3237

3338
### Pre-Requisites
3439
* SDKMAN! installed (recommended):

0 commit comments

Comments
 (0)