Compare Redis and NATS as a pub/sub solution in Actio

[Justus-at-Tazama]

As an Actio platform operator, I want an efficient and robust FRMS so that I can adequately protect my customers and so that I can meet my compliance obligations

Objectives:

1. Manage or eliminate collisions and race conditions through inter-processor pub/sub
2. Be able to report and inspect pile-ups
3. Ensure and maintain optimal throughput

Acceptance criteria

1. Implement NATS pub/sub in 5 rules and one typology as per https://github.com/frmscoe/General-Issues/issues/12
2. Implement Redis pub/sub in the same 5 rules and one typology as per https://github.com/frmscoe/General-Issues/issues/3
3. Create a network map that processes a message set across all 10 rule processors and the two typologies simultaneously.

4. Ingest 10000 transactions into the platform.

   a. No more than 10 different debtors and 10 different creditors to create transaction networks.

5. Compare throughput performance between the two typologies
6. Compare the ability to inspect published volumes in real-time
7. Investigate the ability to generate administrative system alerts when publishing queue capacity reaches a specific set percentage

Proposed rule selection:

• 016 Rule: Transaction convergence - creditor
• 017 Rule: Transaction divergence - Debtor
• 054 Rule: Synthetic data check - Benford's Law - Debtor
• 063 Rule: Synthetic data check - Benford's Law - Creditor
• 090 Rule: Upstream transaction divergence

[Justus-at-Tazama]

NATS selected and implemented