Skip to content

Commit 829f22f

Browse files
authored
Update README.md
1 parent 74f69d9 commit 829f22f

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

packages/core/README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,11 @@
33
The `InboxOutboxModule` is solution designed for NestJS to tackle the challenges of dual write and reliable event delivery in distributed systems. It addresses scenarios where one module emits an integration event, and another module must receive and process this information to maintain system-wide data consistency, which is not possible with a in-memory event bus.
44

55
## Outbox Part Visualization
6-
![outbox](https://github.com/user-attachments/assets/680ee8e7-4ebc-423b-a64f-02d44524044b)
6+
![outbox](https://github.com/user-attachments/assets/83fdb729-70dd-47f9-9449-cd40fe7ddd97)
7+
78

89
## Inbox Part Visualization
9-
![inbox](https://github.com/user-attachments/assets/b59a065d-84ca-44ac-aed0-d66ea4485ae2)
10+
![inbox](https://github.com/user-attachments/assets/fb67a80a-b963-4710-b0d7-a0c28c5fe6a7)
1011

1112

1213
### Problems Addressed
@@ -149,12 +150,12 @@ The module uses a `TransactionalEventEmitter` for reliable event emission. This
149150
name: UserApplicationAssignedEvent.name,
150151
listeners: {
151152
expiresAtTTL: 1000 * 60 * 60 * 24,
152-
maxExecutionTimeTTL: 1000 * 60 * 60 * 24,
153+
maxExecutionTimeTTL: 1000 * 15,
153154
readyToRetryAfterTTL: 10000,
154155
},
155156
},
156157
],
157-
retryEveryMilliseconds: 1000,
158+
retryEveryMilliseconds: 30_000,
158159
maxInboxOutboxTransportEventPerRetry: 10,
159160
};
160161
},

0 commit comments

Comments
 (0)