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.

Sign up for GitHub

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

Jump to bottom

As technology, I should support Application-agnostic stores for logging/reporting databases with generic fact tables #145

Open
2 tasks done
olivierlemee opened this issue Oct 28, 2022 · 3 comments
Open
2 tasks done

As technology, I should support Application-agnostic stores for logging/reporting databases with generic fact tables #145

olivierlemee opened this issue Oct 28, 2022 · 3 comments
Labels
line:mvf Action or item managed via the MVF production line dedicated to prototypes delivery priority:high High priority for treatment type:feature Required behavior/compliance waited from a system or technology (performance, architecture, privacy)
Milestone
OS MVF V0 - Frame...

Comments

@olivierlemee
Copy link
Collaborator

olivierlemee commented Oct 28, 2022 •
edited
Loading

https://www.notion.so/cybnity/485-f3f074c0e8c74aa28f6e39d933fe00f7

REQ_ROB_3 : Use a generic fact table (application-agnostic structure) approach for any type of data type with structural versioning model (avoid sequential version numbers). This type of data structure (schema design) is used mainly for states persistence databases saving the data changes (optimized for insertion; one collection per type of fact) as reference for the processors which generate/refresh the View databases (see REQ_CONS_8 requirement).

GENERIC FACT TABLE

  • A object type table supporting any name of data type (e.g business model object)
  • a fact table ensuring unicity of a fact object and based on an object type, including JSON fields in fact table as blob (e.g binary JSON type cell, or JSON object as strings)
    • User Interactions Space system (docker image based on Redis cluster "RT redis streamed event store") based on Kubernetes and Helm configuration
    • Generic fact structure regarding any Event Store as application-agnostic store

tech: redis, mongo, influx, java
@olivierlemee olivierlemee added this to the OS MVF V0 - Framework milestone Oct 28, 2022
@olivierlemee olivierlemee added line:mvf Action or item managed via the MVF production line dedicated to prototypes delivery type:feature Required behavior/compliance waited from a system or technology (performance, architecture, privacy) labels Nov 3, 2022
@olivierlemee olivierlemee added priority:moderate Moderate priority for treatment priority:high High priority for treatment and removed priority:low Low priority for treatment priority:moderate Moderate priority for treatment labels Nov 24, 2022
@olivierlemee olivierlemee moved this from Backlog to Waiting for coding in Open Source Foundation Pipeline Mar 2, 2023
@olivierlemee
Copy link
Collaborator Author

FactRecord structure design.

@olivierlemee
Copy link
Collaborator Author

objects design and unit tests ok

@olivierlemee
Copy link
Collaborator Author

factRecord and elements with unit tests and repos/store basic contract coded

@olivierlemee olivierlemee moved this from Waiting for coding to Coding in Open Source Foundation Pipeline Mar 8, 2023
@olivierlemee olivierlemee moved this from Coding to Ready for UAT stage in Open Source Foundation Pipeline Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
line:mvf Action or item managed via the MVF production line dedicated to prototypes delivery priority:high High priority for treatment type:feature Required behavior/compliance waited from a system or technology (performance, architecture, privacy)
Projects
Open Source Foundation Pipeline
Status: Ready for UAT stage
Milestone
OS MVF V0 - Framework Stream
Development

No branches or pull requests
1 participant
@olivierlemee