Skip to content

Commit 9033629

Browse files
committed
Add diagrams
1 parent 226538f commit 9033629

File tree

4 files changed

+240
-23
lines changed

4 files changed

+240
-23
lines changed

articles/iot-operations/connect-to-cloud/howto-dataflow-graph-wasm.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -498,9 +498,9 @@ The graph uses specialized modules from the [operators directory](https://github
498498

499499
The following diagram shows the data flow through the various processing modules:
500500

501-
<!-- TODO: Add complex graph YAML definition and explanation -->
501+
:::image type="content" source="media/howto-dataflow-graph-wasm/wasm-dataflow-graph-complex.svg" alt-text="Diagram showing a complex data flow graph example with multiple modules" border="false":::
502502

503-
```mermaid
503+
<!-- ```mermaid
504504
graph TD
505505
source["source"]
506506
delay["module-window/delay"]
@@ -534,7 +534,7 @@ graph TD
534534
concatenate --> accumulate_collection
535535
accumulate_collection --> map_enrichment
536536
map_enrichment --> sink
537-
```
537+
``` -->
538538
539539
As shown in the diagram, data flows from a single source through multiple processing stages:
540540

articles/iot-operations/connect-to-cloud/howto-develop-wasm-modules.md

Lines changed: 33 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -622,36 +622,49 @@ The relationship between graph definitions and Azure IoT Operations data flow gr
622622
5. **Runtime deployment**: The data flow engine pulls the artifacts from the registry and deploys them
623623
6. **Endpoint mapping**: The abstract source/sink operations in your graph connect to actual MQTT topics, Azure Event Hubs, or other data sources
624624

625-
```mermaid
625+
For example, this diagram illustrates the relationship between graph definitions, WASM modules, and data flow graphs:
626+
627+
:::image type="content" source="media/howto-develop-wasm-modules/wasm-dataflow-overall-architecture.svg" alt-text="Diagram showing the relationship between graph definitions, WASM modules, and data flow graphs" border="false":::
628+
629+
<!-- ```mermaid
626630
graph LR
627631
subgraph "Development"
628632
YML[Graph Definition YAML]
629-
WASM[WASM Modules]
633+
WASM1[Temperature Module]
634+
WASM2[Filter Module]
635+
WASM3[Analytics Module]
630636
end
631637

632638
subgraph "Registry (ACR)"
633-
OCI1[Graph Definition OCI]
634-
OCI2[WASM Module OCI]
635-
end
636-
637-
subgraph "Graph Definition (YAML)"
638-
S[source] --> M[map operator]
639-
M --> K[sink]
639+
OCI1[Graph:1.1.0]
640+
OCI2[Temperature:1.0.0]
641+
OCI3[Filter:2.1.0]
642+
OCI4[Analytics:1.5.0]
640643
end
641644

642-
subgraph "Data Flow Graph Resource"
643-
MQTT[MQTT Source] --> G[Graph Processor]
644-
G --> DEST[Destination]
645+
subgraph "Data Flow Graph"
646+
MQTT[Source Endpoint]
647+
subgraph GDE["Graph Execution"]
648+
S[source] --> M1[temperature operator]
649+
M1 --> M2[filter operator]
650+
M2 --> M3[analytics operator]
651+
M3 --> K[sink]
652+
end
653+
DEST[Destination Endpoint]
654+
655+
MQTT --> S
656+
K --> DEST
645657
end
646658

647-
YML --> OCI1
648-
WASM --> OCI2
649-
OCI1 --> S
650-
OCI2 --> M
651-
S -.wraps to.-> MQTT
652-
K -.wraps to.-> DEST
653-
M -.runs as.-> G
654-
```
659+
YML -.-> OCI1
660+
WASM1 -.-> OCI2
661+
WASM2 -.-> OCI3
662+
WASM3 -.-> OCI4
663+
OCI1 -.-> GDE
664+
OCI2 -.-> M1
665+
OCI3 -.-> M2
666+
OCI4 -.-> M3
667+
``` -->
655668
656669
### Registry deployment
657670

articles/iot-operations/connect-to-cloud/media/howto-dataflow-graph-wasm/wasm-dataflow-graph-complex.svg

Lines changed: 102 additions & 0 deletions
Loading

articles/iot-operations/connect-to-cloud/media/howto-develop-wasm-modules/wasm-dataflow-overall-architecture.svg

Lines changed: 102 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)