KSchlobohm
commented
1 year ago The data stored in Azure Cache for Redis can be replicated across regions. This sample chooses not to implement this feature as the features are not appropriate for the Relecloud scenario.
To reach this decision you must examine the data that you store in Azure Cache for Redis to understand whether additional complexity adds value to your scenario.
- Cached Concert details - These details offload pressure from the SQL server by periodically caching results from the SQL database for our most frequently executed query. We expect the cache to be repopulated in the new region on demand during a fail-over event.
- MSAL tokens - These tokens are issued by Azure AD so that the web app can make tokens to the web API app on behalf of the currently authenticated user. During a failover we do not expect users will have to reauthenticate because they have already completed Single Sign On, and we expect the Microsoft.Identity.Web library will retrieve new MSAL tokens as needed to authenticate to the web API.
- Cart info - Each user of the Relecloud system may have tickets in their cart at the time of a failover event. However, this data is typically short lived and the cost of keeping two data regions in sync increases as the data between them becomes more frequently synced. For simplicity, we accept that customers will lose their cart information and must re-add tickets to their cart if a fail-over happens.
If you choose to implement regional data consistency for your scenario you should review these documents for options.
The multiregional deployment should demonstrate how data is kept in sync between regions.