Story: Investigate Backend Needs

[sah7829]

Investigate Backend Needs

As a developer, I want understand our needs for storing and archiving data, so that we can build a robust backend that can satisfy those needs.

Associated Epic: Requirements - Project Setup

Definition of Done

• [ ] Acceptance criteria defined
• [ ] Solution tasks specified
• [ ] Feature branch created
• [ ] Unit tests written
• [ ] Solution is code complete, i.e. passes full suite of unit tests
• [ ] Design documents updated if needed
• [ ] Pull request created
• [ ] Code is reviewed
• [ ] Code is merged to dev branch
• [ ] Acceptance criteria is met
• [ ] Feature branch merged into master
• [ ] Feature branch deleted

Acceptance Criteria

• [ ] Backend needs are completely documented and understood
• [ ] Stories are created to satisfy the needs of our backend
• [ ] Investigation has been reviewed and marked as satisfactory by team

[peber7]

Open source Grafana does not have any retention built in, it is purely a data visualization tool. Because we need data retention, we will need a service that is run with Grafana and our frontend to “cache data metrics that Grafana will use”. We will need a a backend to do this.

Some backend options can be found in these documents...

https://docs.google.com/document/d/1O-7ipiRg8vP2rgpdmO3EG_w65uf9_sbsNj-Ye_R0G9s/edit Link to doc

Data Retention Research.pdf

Authentication Micro Service: We will need a microservice in order to authenticate users into the Single Pane of Glass

• This service sill be responsible for handling the SSO and the Grafana authentication

[peber7]

I believe this can be closed as #18 basically build on top of this (or closed when that story is closed)