You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note
During the transfer characterisation performance workstream, it was noted that the kafka key's for position updates were not correctly aligning to the accounts that were being updated. This story is to rectify that, so that congestion in the position handler is removed.
(This code (Kafka.proceed) is stilling in central services shared. This should be removed and added to the central services.)
Acceptance Criteria:
Verify that position events are keyed based on the database position account Id and base on the use case
prepare will be the Payer DFSP position account Id
fulfil will be the Payee DFSP position account Id
Abort will be the Payer DFSP position account id
The following components will need to be updated
Position handler
Fulfil handler
Timeout handler
Integration tests should be added to validate the partitioning strategy. (i.e verify message keys are the account id for the appropriate use case)
Verify that any new queries that are added (e.g. timeout handler to get position account id's) should be cached.
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
Update prepare, fulfil and timeout handler
Verify any newly added queries are cached
Update unit tests
Update integration tests
Done
Acceptance Criteria pass
Designs are up-to date
Unit Tests pass
Integration Tests pass
Code Style & Coverage meets standards
Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
TBD
Pull Requests:
TBD
Follow-up:
N/A
Dependencies:
N/A
Accountability:
Owner: TBC
QA/Review: TBC
The text was updated successfully, but these errors were encountered:
Goal:
As a
<stakeholder|persona>I want to
so that
Note
During the transfer characterisation performance workstream, it was noted that the kafka key's for position updates were not correctly aligning to the accounts that were being updated. This story is to rectify that, so that congestion in the position handler is removed.
(This code (Kafka.proceed) is stilling in central services shared. This should be removed and added to the central services.)
Acceptance Criteria:
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
Done
Pull Requests:
Follow-up:
Dependencies:
Accountability:
The text was updated successfully, but these errors were encountered: