Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider hybrid database implementation utilizing SQL for transactional and NoSQL for logging, auditing, BI/Big-Data, Fraud and Rules #493

Open
elnyry-sam-k opened this issue Oct 5, 2018 · 0 comments
Labels

Comments

@elnyry-sam-k
Copy link
Member

elnyry-sam-k commented Oct 5, 2018

Consider hybrid database implementation utilizing SQL for transactional and NoSQL for logging, auditing, BI/Big-Data, Fraud and Rules

kevin-biot's comment:
All these activities should not be on the main transaction database. Better to simply allow a full or selective sync copy of transaction DB where reports etc are generated from. Lessens risks for operational staff initiating weird and wonderful reports that could hose the transaction DB.

Miller's comment:
In the case of the forensic log, the ability to generated sealed reports should be available without loading the transaction system. The KMS would be touched to verify horizontal log entries, after they are selected, and as they are added to the report, and again to seal the report with a vertical signature. Likewise, reports can be verified via a service that can touch the KMS to verify report signatures and flag report that have been tampered with. This activity should also be outside the transaction system.

old issue - https://github.com/mojaloop/mojaloop/issues/65

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant