| Page Properties | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Background
Outcome of this spike 09/01/2019:
...
Already carried out in Sept 2018 – The outcome was it is achievable, tested with 10K requests and all of them received. TISNEW-2402
Options considered
Option 1: | Option 2: | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Continue without a message bus | Implement a message bus | ||||||||||||
Pros and cons | POSITIVES No dev work required. NEGATIVES No queuing means potential for duplications being added, especially via bulk upload function. No traceability. No restartability. | POSITIVES Addresses all the negatives from Option #1. Future-proofs our development approach further. Could be rolled out elsewhere - e.g. in place of ETLs with the NDW team. NEGATIVES Is a not insignificant amount of development. Need to source the appropriate software to use. Unclear the overall cost of implementation (time and money). | ||||||||||||
Estimated cost |
Problems with discovering and having to fix duplicates caused because of the lack of message bus. |
| ||||||||||||
Status |
|
|
Action items
- Tickets for separate areas where this could be applied so that PO’s can prioritise – Add to Epic TISNEW-2396
- Use TISNEW-2401 to help with spiking and creating further tickets
...