Open
Description
Would it be possible to add an optional prefix to all of the keys in the Redis DB. We already store some other data in Redis, and if you're using clustering then you can only use DB 0, so it would be nice if they didn't overlap. It could be configurable so that it doesn't impact people who don't need it?
Metadata
Metadata
Assignees
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
MichaCo commentedon Oct 17, 2018
I'm not sure if that's really necessary. You can easily craft prefixed cache keys yourself ;)
bencyoung commentedon Oct 17, 2018
That's true, although you'd need to know at the cache consumer side that:
so it means the knowledge has to propagate. It's not a major concern, but more of a nice to have.
MichaCo commentedon Oct 17, 2018
Yup I agree, would be nice to have.
I'll keep it in mind
gautelo commentedon Nov 29, 2018
I support this notion. Alternatively, or in addition, please add a similar option for prefixing regions.
Baune8D commentedon Oct 29, 2019
I also support this, i really feel this feature is missing.
Microsoft.Extensions.Caching.Redis
already have a feature like this usingInstanceName
We run multiple applications on the same Redis instance and use prefixes to seperate applications. It gets really hard to enforce these key prefixes throughout an application without a feature like this.