GitBook: [master] 2 pages modified

docs/message-handlers/ports.md

@@ -1,2 +1,22 @@
 # Ports
 
+Port is the mechanism to establish communication between aggregates. Usually this involves one aggregate who triggered an event and one aggregate which needs to react.
+
+If you feel the need to do more complex interactions, it is advised to use Saga. The reason for this is that ports do not provide a transparent view of the business flow because they do not have persistent state.
+
+## Communication Guide Table
+
+| Triggered by | Description |
+| :--- | :--- |
+| Event | Domain events represent business changes which have already happened |
+
+## Best Practices
+
+{% hint style="success" %}
+**You can/should/must...**
+
+* a port can send a command
+{% endhint %}
+
+
+

docs/message-handlers/sagas.md

@@ -1,2 +1,22 @@
+---
+description: Sometimes called a Process Manager
+---
+
 # Sagas
 
+When we have a workflow, which involves several aggregates it is recommended to have the whole process described in a single place such as а Saga/ProcessManager.
+
+## Communication Guide Table
+
+| Triggered by | Description |
+| :--- | :--- |
+| Event | Domain events represent business changes which have already happened |
+
+## Best Practices
+
+{% hint style="success" %}
+**You can/should/must...**
+
+* a saga **can** send new commands
+{% endhint %}
+