Diagram

Author: alexeyzimarev

README.md

@@ -19,17 +19,46 @@ Here you can use SwaggerUI to initiate commands that will result in events being
 
 ### Example commands
 
-Bookings -> BookRoom (`/bookings/book`)
+#### Bookings -> BookRoom (`/bookings/book`)
 
-This command raises an event, which gets stored in the database. 
-A real-time subscription triggers a projection, which adds or updates two documents in MongoDB: one for the booking and one for the guest.
+- This command raises an event, which gets stored in the database. 
+- A real-time subscription triggers a projection, which adds or updates two documents in MongoDB: 
+    - one for the booking 
+    - one for the guest
 
-Bookings.Payments -> RecordPayment (`/recordPayment`)
+#### Bookings.Payments -> RecordPayment (`/recordPayment`)
 
-When this command is executed, it raises a `PaymentRecorded` event, which gets persisted to the database.
-A gateway inside the Payments service subscribes to this event and publishes an integration event to RabbitMQ.
-An integration RabbitMQ subscription receives the integration event and calls the Bookings service to execute the `RecordPayment` command, so it acts as a Reactor.
-When that command gets executed, it raises a `PaymentRecorded` event, which gets persisted to the database. It might also raise a `BookingFullyPaid` or `BookingOverpaid` events, depending on the amount.
-Those new events are projected to MongoDB document in the `Bookings` collection using the read-model subscription.
+- When this command is executed, it raises a `PaymentRecorded` event, which gets persisted to the database.
+- A gateway inside the Payments service subscribes to this event and publishes an integration event to RabbitMQ.
+- An integration RabbitMQ subscription receives the integration event and calls the Bookings service to execute the `RecordPayment` command, so it acts as a Reactor.
+- When that command gets executed, it raises a `PaymentRecorded` event, which gets persisted to the database. It might also raise a `BookingFullyPaid` or `BookingOverpaid` events, depending on the amount.
+- Those new events are projected to MongoDB document in the `Bookings` collection using the read-model subscription.
 
-Bookings.Payments -> `CommandService:RecordPayment` -> `PaymentRecorded` -> `IntegrationSubscription` -> `BookingPaymentRecorded` -> Bookings -> RabbitMQSubscription -> `PaymentsIntegrationHandler` -> `BookingsCommandService:OnExisting<RecordPayment>` -> `V1.PaymentRecorded` -> `BookingState:On<V1.PaymentRecorded>`-> `V1.BookingFullyPaid` -> `BookingStateProjection:On<V1.PaymentRecorded>` -> `BookingStateProjection:On<V1.BookingFullyPaid>`
+```mermaid
+graph TB
+    HTTP --> RecordPayment
+    subgraph Payments 
+    direction LR
+    RecordPayment -- aggregate --> PaymentRecorded[PaymentRecorded<br>domain event]
+    Reactor --> PR[PaymentRecorded<br>integration event]
+    end
+    subgraph Postgres
+    PaymentRecorded -- eventstore --> PGSQL[(PGSQL)]
+    PGSQL -- gateway --> Reactor
+    end
+    subgraph Broker
+    PR --> RabbitMQ[[RabbitmQ]]
+    end
+    subgraph Bookings
+    direction RL
+    RabbitMQ -- subscription --> IH[Integration<br>handler]
+    IH --> RP[RecordPayment]
+    RP -- aggregate --> PR1[PaymentRecorded]
+    PR1 -- eventstore --> PGSQL
+    PGSQL -- subscription --> Projections
+    end
+    subgraph MongoDB
+    Projections --> BC[(BookingState)]
+    Projections --> MB[(MyBookings)]
+    end
+```