learningcom / learning.eventstore Goto Github PK

I'm interesting in using Redis as an event store and read your article at:
https://medium.com/lcom-techblog/scalable-microservices-with-event-sourcing-and-redis-6aa245574db0.

One thing not mentioned in the article or anywhere here that I can see is: Redis Persistence. I presume Redis must be configured to persist to disk, no? Otherwise, if Redis were to go down you would lose all your event data.

Can you confirm that this is a requirement? And if so, what persistence strategy is recommended?

Somewhat unrelated, but I would also assume that if message sequence is important, a subscriber should only have one consumer. Otherwise, if there are multiple consumers you couldn't guarantee event sequence, no?

Hi,
First of all I would like to say that Learning.EventStore is really awesome package. Well done.
I have a small question about polling unprocessed messages from published Q.
While my service is down, the publish Q in Redis still collecte event messages as expected.
Once my service subscribe again (after recovery) via RedisEventSubscriber, the published Q still contains all messages but my handler does not getting them (until new event/message pushed).
What can I do about it?
How can I get them after recovery?

Thanks.

Have you considered supporting this Redis data type for event sourcing?

Thanks