This page captures key decisions made in the course of development.
Decision | Date (est) | Parties | Rationale | Options considered |
|---|---|---|---|---|
AWS hosting | Spring 2022 | Scrum team - decision makers | Given our product will spend most of its time inactive, periodically scaling up in response to large data submissions, AWS Lambda is the best fit to design for minimal compute cost. | OpenShift OCP, AWS LZ2 |
API upload for all supported file types | Oct 2023 | Scrum team - decision makers | The AWS SFTP transfer family is a significant cost so we would like to provide users with options to replace it. Since BCM submits file that we already have a parser for, a file upload API represents minimal impact to existing behaviour. | We were unable to identify an existing SFTP server we could pull from (unable to eliminate the transfer family). We considered whether our users could adopt a JSON-based API, but concluded the timeline for BCM to be able to do this would be too far out. |
Product name: Discrepancy Report On Payments (DROP) | Oct 2023 | Scrum team - informed | N/A | N/A |
S3 Glacier for longterm storage | Oct 2023 | Scrum team - decision makers | See CCFPCM-648 - Getting issue details... STATUS | |