DO NOT MERGE Pluggable message stores experiment #1142
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to be able to use different implementation for message store,
the message store module is not called directly from rabbit_variable_queue,
instead it can be configured with application environment and will
be saved in a message store supervisor.
The message store has a bit more complex behaviour when confirming messages to be written on disk synchronously. It still needs to be described in the behaviour module comments.
This is a part of an experiment to replace a message store.
The replacement module using ElevelDB can be found in this repo