Hi Adam.

That is a great question! I am a big fan of Redis, which is why me and my team succesfully has used StackExchange.Redis for similar purposes in larger scale Episerver CMS and Episerver Commerce projects. Would recommend you to have a look at Episervers Event Broker and the WcfEventProvider implementation in EPiServer.Events.Providers. Since it's considered an Episerver Internal, you'll have to step carefully. Have in mind that Episerver's EventProviders aren't interchangeable per se, so you'll have to work look in to replacing the EPiServer.Events.Providers.Internal.EventProviderServiceFactory (ResolveDefaultProvider) to get your implementation considered runtime. 

Would love to hear more about how it goes! Let me know if you have additioonal questions.

/Casper Aagaard Rasmussen

Hey,

Thansk for replying.  Looking at https://azure.microsoft.com/en-gb/solutions/architecture/digital-marketing-episerver/ it suggests that the code is already written and part of Episerver.

Hi Adam.

That is, to my recollection, not correctly documented. Episerver DXC Service uses the Azure ServiceBus (hence not Redis) for distribution of events in their true cloud setup. You can have a look at Episerver.Azure, which includes an AzureEventProvider relying on Microsoft's own Microsoft.ServiceBus code APIs. Probably not an option for you, since you're using Amazon, which was why I did not mention this package in the first place.

Hope that clarified your question.

/Casper Aagaard Rasmussen

@Adam, there are a number of out-of-the-box usecases for Redis with Episerver e.g. out-of-process session storage. We don't however ship with a Redis content cache at the moment, but rely on service bus for invalidation messages as Casper mentions.