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.

Sign up for GitHub

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

Jump to bottom

Provide guidance for NATS streaming store selection #316

Open

ColinSullivan1 opened this issue Mar 1, 2018 · 1 comment

Member

ColinSullivan1 commented Mar 1, 2018 •

edited

Loading

We should provide some guidance on when to use which store.

Memory

Pure speed
Do not require at least once delivery guarantees. This may be for use cases where NATS streaming if being used fo it's features (e.g. replay, rate limiting) rather than persistence requirements, and the system can rebuild state upon failure.

File

Require at least once delivery.
High throughput requirements and moderate number of channels

Database

Have strong requirements around data backup
High number of channels
Moderate/Low throughput requirements.

CC @kozlovic for comment.

Note, saving off this content here until the site is refactored (otherwise I'd have just submitted a PR).

Member

gcolliso commented Jun 17, 2019

@kozlovic did you have any additional information wrt when and which store to use?

I can add the above comments from Colin to the Supported Stores document https://nats-io.github.io/docs/nats_streaming/clustering/supported-stores.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment