Feature Request: Redis service and cache API

[c9mb]

Issue description

Not a well thought out feature requests, and more of a conceptual idea as a suggestion.

Currently, there are application runtime cache options available via an API, but not persistent cache.

An Azure Redis service for a site (similar to how an Azure BlobStorage service is now provided) would offer the opportunity for persistent cache, to help reduce database latency, and could be enhanced with a standard API and a provider that makes it fairly seamless to move between runtime and persistent cache.

I currently use my own Azure Redis configurations and custom code when needed, and it works well (albeit, you need a min 2-node config) but it would be nice if this was an add-on that could be configured in the portal on an as-needs basis, and accessed via a standard API.

[umbrabot]

Hiya @c9mbundy,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[c9mb]

@umbrabot still relevant

I believe that this Feature-Request is still valid, and at least worthy of consideration.

Azure-Redis as an optional service for Umbraco-Cloud would be a useful addition for providing persistent cached data, that can be restored to local cache on restart.

[sajumb]

Thanks @c9mbundy. Sorry for not responding to this sooner. This is definitely something that we consider and might be looking into after after we have launched the US region later this year.