When you upload your site on several instances in Azure or want to scale the instances, you need to prepare the communication infrastructure to transmit messages between the nodes. For example, to communicate cache invalidation. Sitefinity CMS uses Redis message sender that you must configure for NLB communication in Azure Web Apps.
NOTE: In Sitefinity CMS Redis Cache is used for NLB communication only. It is not used for persisting items in cache.
Perform the following:
ConnectionString
$redisPrimaryKey@$redisCacheName.redis.cache.windows.net?ssl=true
NOTE: Because Redis Cache is not used for storing cache data, but for NLB communication only, Sitefinity CMS can work with the minimum pricing tier for Azure Redis – Basic tier for development purposes. If you want to achieve failover redundancy for a production environment, we recommend using at least Azure Standard Pricing tier (C0+). For more information about the different pricing tires, see Redis Cache Pricing.
NOTE: Sitefinity CMS and Redis are completely decoupled and they can work both (or one of them) on-premises infrastructure.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.
This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important