A centralized database that collects and potentially pushes data out to smaller, in-memory flux-accounting databases should be well-documented and designed.
While there should be documentation on how its planned to be designed, its deployment instructions, and any APIs that interact with it, this issue should just focus on its design, schema, and how we might leave room for future schema versions and potential changes to this DB.
Some relevant sections might include:
- purpose/background
- functional/operational goals
- design principles
- the existing SQLite database model
- a proposed PostgreSQL architecture/schema
- import/export strategy
- schema evolution strategy/version tracking
A centralized database that collects and potentially pushes data out to smaller, in-memory flux-accounting databases should be well-documented and designed.
While there should be documentation on how its planned to be designed, its deployment instructions, and any APIs that interact with it, this issue should just focus on its design, schema, and how we might leave room for future schema versions and potential changes to this DB.
Some relevant sections might include: