Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: CFA 2020R4
    • Component/s: None
    • Labels:
    • Sprint:
      CFAMX 2020R4 Sprint 1, CFAMX 2020R4 Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      As a developer I want to implement API throttling so that I can protect InFORM from being overwhelmed during peak periods

      Notes

      • Caner Saritac previously did some research into this, CFAMX-7263
      • Initially this will be implemented for the new Waste API's that are being developed as a part of this feature
        • GET reason codes
        • GET waste item details
        • POST waste items
      • CFA have asked that the Waste API be opened up/made more robust, in order to support in restaurant initiatives, one of these is automated waste tracking
      • Assuming:
        • 2,200 restaurants
        • 60 automated waste transactions per hour
        • = 2,200 * 60 = 132,000/hour, 2,200/minute, 37/second

      Acceptance Criteria

      1. Confirm that the new API throttling mechanism supports GET calls
      2. Confirm that the new API throttling mechanism supports POST calls
      3. Confirm that the new API throttling mechanism is thoroughly documented
      4. Confirm that the new API throttling mechanism supports being expanded beyond the Waste APIs
      5. Confirm that the new API throttling mechanism provides data on how many calls were made within a specific time period
      6. Confirm that the new API throttling mechanism supports some sort of reset
      7. Confirm that the new API throttling mechanism works behind the load balancer
      8. Confirm that the new API throttling mechanism has some redundancy built into it

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jason.powell Jason Powell
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 20h
                  20h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 9h 10m Time Not Required
                  9h 10m

                    PagerDuty

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