Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Redis as a persistence layer #12

Merged
merged 1 commit into from
Aug 18, 2019
Merged

Add Redis as a persistence layer #12

merged 1 commit into from
Aug 18, 2019

Conversation

edisonywh
Copy link
Owner

By default, the events emitted from your app will be stored in an
in-memory Queue, which will get processed by Rocketman threaded
workers.

However this also means that if your app dies with events still in your
job queue, your emitted events which are stored in-memory will be lost.

That is obviously not desirable, so that's why Rocketman (this commit) ships with an
option to use Redis as your backing storage mechanism.

By default, the events emitted from your app will be stored in an
in-memory `Queue`, which will get processed by Rocketman threaded
workers.

However this also means that if your app dies with events still in your
job queue, your emitted events which are stored in-memory will be lost.

That is obviously not desirable, so that's why Rocketman (this commit) ships with an
option to use `Redis` as your backing storage mechanism.
@edisonywh edisonywh merged commit a5fadd6 into master Aug 18, 2019
@edisonywh edisonywh deleted the persistence/redis branch August 18, 2019 08:24
@edisonywh edisonywh mentioned this pull request Aug 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant