Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Page Properties
label


Status
Status
colourGreen
titleDecided
Decision leaderPaul Hoang (Unlicensed)
Contributors
TIS Team
Due date
OutcomeMessage bus is the agreed way forward. PoC carried out successfully.


Background

Outcome of this spike 09/01/2019:

...


Option 1:Option 2:
DescriptionContinue without a message busImplement 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
Status
colourYELLOW
titleMEDIUM
 (Time and Effort)
Problems with discovering and having to fix duplicates caused because of the lack of message bus.
Status
colourRED
titleLARGE
 (Time and Cost)
Status
Status
colourYellow
titleIn progress
Status
colourRed
titleto do

...