Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-11426

Implement Redis caching in Mobile for configuration

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      CFAMX 2021R1 SA Sprint 1
    • Story Points:
      5
    • Work Type Classification:
      Sustaining

      Description

      This story is to implement Redis caching similar to what was developed for the new API for the Mobile configuration database calls.

      Need to implement IsCacheAvailable method in Mobile.
      Need to cache configuration data in Redis
      Need a way to invalidate cache to replace values when configurations change

        Attachments

          Issue Links

          implements

          Feature Request - CFAMX-6647 Implement HA Caching

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Customer Defect - CFAMX-13503 Redis cache - template override configuration is not applied

          • Major - Major loss of function.
          • Done
          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                Corey.Amend Corey Amend (Inactive)
                Reporter:
                Corey.Amend Corey Amend (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 48h
                  48h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 29h 17m Time Not Required
                  29h 17m

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.