[ARCHIVE] July2020-3.1 Banking APIs: Performance

Note: This article has been archived. It relates to a historical event that has been resolved.

Archived Text

Summary

ADRs experienced slow response times on requests to DH’s Banking API endpoints. In some instances this resulted in timeout errors.

Incidents occurred when:

1. ADRs requested large volumes of data (e.g. historical transactions over two years); or
2. Data requests were made to DH’s services that needed to start up or warm up to service initial and subsequent requests for data.

Participants involved

ADR & DH

Workaround

Incidents were resolved through a combination of: 1. ADRs optimising the volume of data requested in a single API call through: i. Configuring and reducing the page-size of requests; and ii. Limiting the time period of requested data. 2. DHs implementing a series of performance improvement configurations including: i.Ensuring API services are already started and running to respond to initial and subsequent requests; and ii.Optimising or disabling caching implementations.

Occurrence A

ADRs observed longer than expected response times to some Banking APIs resulting in 504 timeout errors from DH API implementations.

Impact

Ability to collect consumer data intermittently disrupted.

Occurrence B

Responses from Get Transactions For Account and Get Transaction Details endpoints were slow causing internal components to timeout after a period of time (60 seconds in reported incident). DH fix successfully increased the speed of the responses to 1000 transactions within 1 second (+/- 200ms).

Impact

ADR requests for accounts with certain parameters (page-size more than 500 and oldest date more than 12 months) were resulting in timeout errors blocking data sharing between the DH and ADR.

Occurrence C

Some requests to the DH Get Transactions For Account and Get Transaction Details API endpoints were slow or unsuccessful and consequently leading to a failure to share data. Subsequent requests were successful with data being shared in under 2 seconds.

The DH’s root cause analysis was that the DH's caching implementation was filling up and reloading at predefined intervals.

Impact

Initial requests to the DH transaction API endpoints resulted in failure to share data.

Occurrence D

Initial requests to the DH Banking API endpoints were slow, with a response time of more than 14.9 seconds. The subsequent requests were also slow with the response time of ~6.8 seconds.

The issue was related to the potential caching/warm up considerations due to the infrequency of calls made in Production.

Impact

Slow data sharing.