Closed elliott-beach closed 6 years ago
@elliott-beach Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.
@elliott-beach I agree 100%. This needs to be clarified. Redis is definitely an in-memory cache. I haven't tested it myself but looks like even the SQL Server Session State provider now supports an in-memory configuration with In-Memory OLTP configuration. I'll get this updated,
@elliott-beach I added some clarification to this topic. It should be live tomorrow. Ideally, we would want to point to performance comparisons between the providers to show where the Azure Redis Cache provider fits into the big picture. However, at this time we don't have such a performance comparison. Back in 2013 some comparisons were compiled and posted on Stackoverflow. These did show Redis Cache on top for the most part, but these could be obsolete with the latest providers. If you have any more questions about this let me know.
The first sentence of the docs says: "
Wow, I am excited to learn about this! But that sentence is misleading because Redis is an in-memory cache (with persistence), and the documentation should say that up front. Especially when the following paragraph is explaining the different options for session providers, it really needs to say where Redis fits into the big picture.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.