Skip to content

Commit 2f5e300

Browse files
committed
rabbitmq persistence in readme
1 parent d841ebb commit 2f5e300

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

readme.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,9 @@ to consumer if RabbitMQ server is running.
297297

298298
### What will happen if the RabbitMQ server is shutdown?
299299
No events will be pushed to the consumer. If there is any stored events in RabbitMQ server memory before shutdown those
300-
will be lost too.
300+
will be lost too.
301+
**Note:** It is possible to overcome this limitation by using persistence mechanism which will keep safe from losing stored events.
302+
This mechanism is not implemented here that's why am skipping the issue.
301303

302304
### What will happen with the events when all product-service instance are shutdown?
303305
RabbitMQ keeping all the events in itself will wait for any product-service instance when a product-service instance

0 commit comments

Comments
 (0)