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:
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.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity