-
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
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
- Confirm that the new API throttling mechanism supports GET calls
- Confirm that the new API throttling mechanism supports POST calls
- Confirm that the new API throttling mechanism is thoroughly documented
- Confirm that the new API throttling mechanism supports being expanded beyond the Waste APIs
- Confirm that the new API throttling mechanism provides data on how many calls were made within a specific time period
- Confirm that the new API throttling mechanism supports some sort of reset
- Confirm that the new API throttling mechanism works behind the load balancer
- Confirm that the new API throttling mechanism has some redundancy built into it
- implements
-
CFAMX-10366 Make the Waste API robust enough for chain-wide usage by Automated Holding Assistant to inject waste data
- Closed
There are no Sub-Tasks for this issue.