-
Notifications
You must be signed in to change notification settings - Fork 197
DOC-5192 added C# production usage page #1491
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. One suggestion, though: can you use unique IDs for each checklist
short code use? If you don't, then the stored status will apply to every page that uses the short code.
D'oh! Yeah, I completely forgot about that (I copied/pasted the top bit of the page, as you probably realised). I've fixed it now and I'll try to remember it for the remaining pages. |
there are other events besides server maintenance events. Events would be useful in production env for instance in terms of logging/monitoring underlying connection lifetimes and topology changes and possible issues around it. 👉 https://stackexchange.github.io/StackExchange.Redis/Events There is also timeouts to be aware of and might require an adjustment depending on use case and environment though they already have their own default values,, like i think that is pretty much all i can share for an initial set of recommendations. |
DOC-5192
This is intended to give recommendations for production usage like the Jedis page, but it's actually quite difficult to find any advice for NRedisStack :-) (Client-side caching isn't implemented, and most of the stuff recommended for Jedis either happens by default or is handled automatically.)
I'd love to hear ideas - if we can't think of any more recommendations, then maybe this page isn't necessary for NRedisStack and we should just have a short section about this stuff in the landing page.