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

architecture (living task) #18

Open
Joel-Haeberli opened this issue Jun 12, 2023 · 2 comments
Open

architecture (living task) #18

Joel-Haeberli opened this issue Jun 12, 2023 · 2 comments
Assignees
Labels
architecture Everything that has to do with the architecture of momentum backend

Comments

@Joel-Haeberli
Copy link
Contributor

Joel-Haeberli commented Jun 12, 2023

As Architect I want a clear idea of the different components and requirements of momentum, so that quality can be guaranteed.

Acceptance Criteria:

  • Its defined how we do...
    • Logging (How do we log in momentum)
    • Monitoring (How do we monitor momentum)
    • Testing (How do we test momentum)
      • how to run tests which use filesystem interactions using GitHub actions
    • Security aspects (How do we encrypt, key management)
    • Documentation (What needs to be documented)

For logging, monitoring and testing must be done some research in the golang world to find out best practices.

@Joel-Haeberli Joel-Haeberli added architecture Everything that has to do with the architecture of momentum backend labels Jun 12, 2023
@Joel-Haeberli Joel-Haeberli self-assigned this Jun 12, 2023
@Joel-Haeberli
Copy link
Contributor Author

@Joel-Haeberli
Copy link
Contributor Author

@Joel-Haeberli Joel-Haeberli changed the title Architecture architecture Jun 12, 2023
@Joel-Haeberli Joel-Haeberli changed the title architecture architecture (living task) Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture Everything that has to do with the architecture of momentum backend
Projects
No open projects
Status: Todo
Development

No branches or pull requests

1 participant