rl15
commented
3 years ago Deprecated in Fortnightly PSD/DT1/DT4/DT6 meeting on 25th Aug
Open rl15 opened 3 years ago
rl15
commented
3 years ago Deprecated in Fortnightly PSD/DT1/DT4/DT6 meeting on 25th Aug
Description DPL-041 | Research: Allow PAM (Rhys) to consume the 'labwhere_uploaded_from_manifest' events without loosing the insert via builders into MLWH
As per the original intention of the MQ architecture PAM (DT4) would like to consume from the events Q directly rather than looking for update from database.
Who the primary contacts are for this work Callum S (PAM) Rhys (PAM) James G (PSG) 1 Katy T (PSG)1
*1 first discussion to generate options below
Options
1) New Q
[ ] PSG create new Q on our exchange
[ ] New credentials for PAM
Simplest approach
If teh consumer stops messages will back up and consume disk space. Mitigation set a maximum Time To Live (TTL)
2) New host PSD maintained
[ ] Create separate Rabbit MQ for customers
[ ] New credentials for PAM
Better separation
More PSD infrastructure to manage on FCE
3) New Host PAM maintained
[ ] New credentials for PAM PAM create separate Rabbit MQ used only by them
[ ] New credentials for PAM PSG shovel 'labwhere_uploaded_from_manifest' (and others in time?) events form existing PSD exchange to PAM RMQ instance
Best seperation o Shovel could til back up so need to agree policy what would be the expected behavior o Maintenance burden moved from PSD to PAM
Additional context or information This relates to enabling Important Samples (See backlog item GPL-843 Flag 'Must sequence' and 'preferentially sequence' samples in box buster #51 and its associates)