Skip to content
This repository has been archived by the owner on Jan 5, 2022. It is now read-only.

Architectural changes for future work #333

Open
peetucket opened this issue Apr 3, 2019 · 1 comment
Open

Architectural changes for future work #333

peetucket opened this issue Apr 3, 2019 · 1 comment
Labels
analysis

Comments

@peetucket
Copy link
Contributor

peetucket commented Apr 3, 2019 •
edited
Loading

  • validate data upon creation
  • reconsider use of Neptune or triple store as canonical data store (to avoid latency problems with data insert ordering not guaranteed)
  • denormalize postgres database to optimize for reporting
  • make reporting asynchronous (so users can be notified when their reports are ready for long running reports)
@peetucket
Copy link
Contributor Author

Also see https://docs.google.com/document/d/1nMgthNtSLVYJAG_ENj9HzLc_Cwe88nvrhCXQN8bOEwc

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
analysis
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@peetucket